Authenticated file disclosure via incomplete symlink resolution
Published Jan 21, 2026 · Updated Jan 21, 2026
Path traversal in Backstage before 0.1.17 allows remote authenticated users to read files outside designated directories via crafted symlinks. resolveSafeChildPath accepted symlink chains and dangling links when real-path resolution failed, allowing their eventual targets to escape the validated base directory. Template creation or another backend path that accepts attacker-controlled symlinks is required; exploitation exposes files readable by the Backstage process.
Summary
What happened
Path traversal in Backstage before 0.1.17 allows remote authenticated users to read files outside designated directories via crafted symlinks. resolveSafeChildPath accepted symlink chains and dangling links when real-path resolution failed, allowing their eventual targets to escape the validated base directory. Template creation or another backend path that accepts attacker-controlled symlinks is required; exploitation exposes files readable by the Backstage process.
The record
- CVE
- CVE-2026-24047
- Published
- Jan 21, 2026
- Updated
- Jan 21, 2026
- Vendor
- Backstage
- Product
- Backstage
- Classifications
- CWE-59, CWE-61
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 21, 2026CVE publishedPublication date reported by the CVE source.
- Jan 21, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.1.17
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo