Authenticated code execution via MkDocs hooks
Published Jan 30, 2026 · Updated Jan 30, 2026
Code injection in Backstage TechDocs before 1.13.11 and in 1.14.0 allows remote authenticated users to execute Python code. The TechDocs generator passes repository-controlled mkdocs.yml hooks to MkDocs, which imports and runs the referenced Python hook files on the build server. Exploitation requires permission to submit or modify a processed repository and a TechDocs generator configured with runIn local; execution affects the build server.
Summary
What happened
Code injection in Backstage TechDocs before 1.13.11 and in 1.14.0 allows remote authenticated users to execute Python code. The TechDocs generator passes repository-controlled mkdocs.yml hooks to MkDocs, which imports and runs the referenced Python hook files on the build server. Exploitation requires permission to submit or modify a processed repository and a TechDocs generator configured with runIn local; execution affects the build server.
The record
- CVE
- CVE-2026-25153
- Published
- Jan 30, 2026
- Updated
- Jan 30, 2026
- Vendor
- Backstage
- Product
- Backstage
- Classifications
- CWE-94, T1059.006
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 30, 2026CVE publishedPublication date reported by the CVE source.
- Jan 30, 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=< 1.13.11
- Affected versionversion== 1.14.0
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