Backstage · weakness class
File and Path Handling
25 CVEs
Every dot is a CVE in what this vendor ships; the named ones are the most at risk.
Every one of the 25 is a mark on the map. Named now: 1 to 25, most at risk first.
- Path Traversal in @backstage/plugin-scaffolder-backend
- TechDocs mkdocs.yml path traversal
- Path Traversal in @backstage/plugin-scaffolder-backend
- @backstage/plugin-techdocs-node: TechDocs Mkdocs Configuration Key Enables Arbitrary Code Execution
- `@backstage/backend-common` vulnerable to path traversal through symlinks
- Storage bucket Directory Traversal in @backstage/plugin-techdocs-backend
- @backstage/cli-common has a possible `resolveSafeChildPath` Symlink Chain Bypass
- Backstage has a Possible Symlink Path Traversal in Scaffolder Actions
- @backstage/plugin-techdocs-node vulnerable to possible Path Traversal in TechDocs Local Generator
- @backstage/integration: Potential reading of SCM URLs using built in token
- Backstage: Potential file exposure through local TechDocs publisher
- Backstage: TechDocs arbitrary file read via mkdocs snippets
- Backstage: Improper input validation in TechDocs Markdown extension configuration
- Backstage: Improper input validation in TechDocs static content requests
- Backstage: Improper filesystem validation in Bitbucket pull-request scaffolder actions
- Backstage: Improper task state validation in Scaffolder backend
- Backstage: Improper input validation in Confluence to Markdown scaffolder module
- Backstage catalog rules can be bypassed for URL locations using encoded path segments
- Backstage: Improper repository path validation in a Scaffolder backend module
- Backstage: Bypass of MkDocs configuration sanitizer in TechDocs backend
- Backstage: Improper input validation in cloud storage URL readers
- Backstage: Improper authorization enforcement for TechDocs static content
- Backstage: Cloud storage catalog locations may cross configured storage boundaries
- Backstage: Improper input validation in proxy-backend
- Backstage: Inconsistent enforcement of allowed location types during catalog processing
exploited in the wildcheck availableringed, named or not: CyberSIXT has reported on it
Zoom in on the map and the dots under the middle of it are named where they are.
Data as of 2026-11-15. CVE List through 2026-11-15 · EPSS of 2026-11-15 · CISA KEV checked 2026-11-15. Sources: the CVE List, CISA KEV, EPSS, NVD, nuclei templates and public bug bounty data.