GHSA-P75X-JH7P-PPCX

Vulnerability from github – Published: 2026-10-07 16:23 – Updated: 2026-10-07 16:23
VLAI
Summary
Backstage: Bypass of MkDocs configuration sanitizer in TechDocs backend
Details

Impact

Users with the ability to commit changes to a repository that uses TechDocs can circumvent the MkDocs configuration file sanitizer introduced in response to CVE-2026-25153 and execute arbitrary code on the TechDocs backend host during documentation generation.

Patches

Patched in@backstage/plugin-techdocs-node version 1.15.4

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.
  • Limit repository write access to trusted parties, since exploitation requires the ability to commit files to a repository with TechDocs enabled.
  • Review incoming changes to MkDocs configuration files as part of your code review process.
Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "@backstage/plugin-techdocs-node"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.15.4"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-106505"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-426",
      "CWE-436"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-10-07T16:23:52Z",
    "nvd_published_at": "2026-10-06T22:17:05Z",
    "severity": "HIGH"
  },
  "details": "### Impact\n\nUsers with the ability to commit changes to a repository that uses TechDocs can circumvent the MkDocs configuration file sanitizer introduced in response to CVE-2026-25153 and execute arbitrary code on the TechDocs backend host during documentation generation.\n\n### Patches\n\nPatched in`@backstage/plugin-techdocs-node` version `1.15.4`\n\n### Workarounds\n\nIf you cannot upgrade immediately:\n\n- 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.\n- Limit repository write access to trusted parties, since exploitation requires the ability to commit files to a repository with TechDocs enabled.\n- Review incoming changes to MkDocs configuration files as part of your code review process.",
  "id": "GHSA-p75x-jh7p-ppcx",
  "modified": "2026-10-07T16:23:52Z",
  "published": "2026-10-07T16:23:52Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/backstage/backstage/security/advisories/GHSA-p75x-jh7p-ppcx"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-106505"
    },
    {
      "type": "WEB",
      "url": "https://github.com/backstage/backstage/commit/a7d995f11a5d27f0efbdbe8bb6c21b06988c79c9"
    },
    {
      "type": "WEB",
      "url": "https://github.com/backstage/backstage/commit/ef92d3d2b76046205c580e7152956514c15640db"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/backstage/backstage"
    },
    {
      "type": "WEB",
      "url": "https://github.com/backstage/backstage/releases/tag/v1.50.5"
    },
    {
      "type": "WEB",
      "url": "https://github.com/backstage/backstage/releases/tag/v1.54.6"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:L",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Backstage: Bypass of MkDocs configuration sanitizer in TechDocs backend"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Loading…

Loading…

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.


Loading…