GHSA-6jr7-99pf-8vgf

Source

https://github.com/advisories/GHSA-6jr7-99pf-8vgf

Import Source

https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/02/GHSA-6jr7-99pf-8vgf/GHSA-6jr7-99pf-8vgf.json

JSON Data

https://api.osv.dev/v1/vulns/GHSA-6jr7-99pf-8vgf

Aliases

CVE-2026-25153

Published

2026-02-02T20:19:58Z

Modified

2026-02-03T17:51:32.962569Z

Severity

7.7 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:L CVSS Calculator

Summary

@backstage/plugin-techdocs-node vulnerable to arbitrary code execution via MkDocs hooks

Details

Impact

When TechDocs is configured with runIn: local, a malicious actor who can submit or modify a repository's mkdocs.yml file can execute arbitrary Python code on the TechDocs build server via MkDocs hooks configuration.

Patches

Upgrade to @backstage/plugin-techdocs-node version 1.13.11, 1.14.1 or later. The fix introduces an allowlist of supported MkDocs configuration keys. Unsupported configuration keys (including hooks) are now removed from mkdocs.yml before running the generator, with a warning logged to indicate which keys were removed.

Note: Users of @techdocs/cli should also upgrade to the latest version, which includes the fixed @backstage/plugin-techdocs-node dependency.

Workarounds

If you cannot upgrade immediately:

Use Docker mode with restricted access: Configure TechDocs with runIn: docker instead of runIn: local. This provides container isolation, though it does not fully mitigate the risk.
Restrict repository access: Limit who can modify mkdocs.yml files in repositories that TechDocs processes. Only allow trusted contributors.
Manual review: Implement PR review requirements for changes to mkdocs.yml files to detect malicious hooks configurations before they are merged.
Downgrade MkDocs: Use MkDocs < 1.4.0 (e.g., 1.3.1) which does not support hooks. Note: This may limit access to newer MkDocs features.

Note: Building documentation in CI/CD pipelines using @techdocs/cli does not mitigate this vulnerability, as the CLI uses the same vulnerable @backstage/plugin-techdocs-node package.

References

MkDocs Hooks Documentation MkDocs 1.4 Release Notes TechDocs Architecture

Database specific

{
    "nvd_published_at": "2026-01-30T22:15:56Z",
    "cwe_ids": [
        "CWE-94"
    ],
    "severity": "HIGH",
    "github_reviewed": true,
    "github_reviewed_at": "2026-02-02T20:19:58Z"
}

References

Affected packages

npm / @backstage/plugin-techdocs-node

Package

Name: @backstage/plugin-techdocs-node; View open source insights on deps.dev
Purl: pkg:npm/%40backstage/plugin-techdocs-node

Affected ranges

Type: SEMVER
Events: Introduced

1.14.0

Fixed

1.14.1

Affected versions

1.*

1.14.0

Database specific

source

"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/02/GHSA-6jr7-99pf-8vgf/GHSA-6jr7-99pf-8vgf.json"

npm / @backstage/plugin-techdocs-node

Package

Name: @backstage/plugin-techdocs-node; View open source insights on deps.dev
Purl: pkg:npm/%40backstage/plugin-techdocs-node

Affected ranges

Type: SEMVER
Events: Introduced

0Unknown introduced version / All previous versions are affected

Fixed

1.13.11

Database specific

source

"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/02/GHSA-6jr7-99pf-8vgf/GHSA-6jr7-99pf-8vgf.json"