GHSA-Q38J-6VCM-2F5M

Vulnerability from github – Published: 2026-10-07 20:25 – Updated: 2026-10-07 20:25
VLAI
Summary
Backstage: Improper validation of MkDocs plugin configuration in TechDocs
Details

Impact

An authenticated attacker with control over a TechDocs source repository could cause a documentation build to retrieve and publish data from network locations reachable by the build environment. Exposure depends on deployment topology, build mode, and target endpoint protections. Modern cloud metadata services that require tokens or special headers are not directly accessible through the affected behavior.

Patches

Upgrade @backstage/plugin-techdocs-node to a patched version for the applicable release line:

The update removes MkDocs plugins outside the built-in allowlist. To retain additional plugins, review them and configure techdocs.generator.mkdocs.dangerouslyAllowAdditionalPlugins, or supply dangerouslyAllowAdditionalPlugins when creating the generator directly. Plugins supplied through defaultPlugins remain permitted.

Workarounds

  • Restrict control of TechDocs source repositories and catalog registration to trusted maintainers.
  • Run documentation builders with outbound access to private and link-local networks denied.
  • Require token- or header-protected cloud instance metadata services.
Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "@backstage/plugin-techdocs-node"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0.11.12"
            },
            {
              "fixed": "1.14.7"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "npm",
        "name": "@backstage/plugin-techdocs-node"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "1.15.0"
            },
            {
              "fixed": "1.15.5"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-106455"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-918"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-10-07T20:25:19Z",
    "nvd_published_at": "2026-10-06T21:17:15Z",
    "severity": "HIGH"
  },
  "details": "### Impact\n\nAn authenticated attacker with control over a TechDocs source repository could cause a documentation build to retrieve and publish data from network locations reachable by the build environment. Exposure depends on deployment topology, build mode, and target endpoint protections. Modern cloud metadata services that require tokens or special headers are not directly accessible through the affected behavior.\n\n### Patches\n\nUpgrade `@backstage/plugin-techdocs-node` to a patched version for the applicable release line:\n\n- `1.14.x`: upgrade to `1.14.7` or later in that line, available in [Backstage v1.50.6](https://github.com/backstage/backstage/releases/tag/v1.50.6).\n- `1.15.x`: upgrade to `1.15.5` or later, available in [Backstage v1.54.8](https://github.com/backstage/backstage/releases/tag/v1.54.8).\n- Current mainline: upgrade to `2.0.0` or later, available in [Backstage v1.55.0](https://github.com/backstage/backstage/releases/tag/v1.55.0).\n\nThe update removes MkDocs plugins outside the built-in allowlist. To retain additional plugins, review them and configure `techdocs.generator.mkdocs.dangerouslyAllowAdditionalPlugins`, or supply `dangerouslyAllowAdditionalPlugins` when creating the generator directly. Plugins supplied through `defaultPlugins` remain permitted.\n\n### Workarounds\n\n- Restrict control of TechDocs source repositories and catalog registration to trusted maintainers.\n- Run documentation builders with outbound access to private and link-local networks denied.\n- Require token- or header-protected cloud instance metadata services.",
  "id": "GHSA-q38j-6vcm-2f5m",
  "modified": "2026-10-07T20:25:19Z",
  "published": "2026-10-07T20:25:19Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/backstage/backstage/security/advisories/GHSA-q38j-6vcm-2f5m"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-106455"
    },
    {
      "type": "WEB",
      "url": "https://github.com/backstage/backstage/commit/28aa82ae2815988721dd7bbf43cd69c431dcd71b"
    },
    {
      "type": "WEB",
      "url": "https://github.com/backstage/backstage/commit/9f76ea445088961f68c364764cc4b7734f368fc0"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/backstage/backstage"
    },
    {
      "type": "WEB",
      "url": "https://github.com/backstage/backstage/releases/tag/v1.50.6"
    },
    {
      "type": "WEB",
      "url": "https://github.com/backstage/backstage/releases/tag/v1.54.8"
    },
    {
      "type": "WEB",
      "url": "https://github.com/backstage/backstage/releases/tag/v1.55.0"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Backstage: Improper validation of MkDocs plugin configuration in TechDocs"
}



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…