GHSA-RG9R-HR7G-5GC2
Vulnerability from github – Published: 2026-10-07 18:00 – Updated: 2026-10-07 18:00Impact
An authenticated user with access to one TechDocs documentation site could craft a URL able to read documentation belonging to a different entity. This only affects deployments using the external TechDocs builder with an external storage provider (S3, GCS, etc.) and the permission framework enabled. Instances that do not use the permission framework are unaffected, since TechDocs content is visible to all authenticated users by design.
Patches
Patched in @backstage/plugin-techdocs-backend version 2.2.4
Workarounds
- None other than upgrading. Deployments that serve TechDocs from local storage are not affected.
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "@backstage/plugin-techdocs-backend"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.2.4"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-106489"
],
"database_specific": {
"cwe_ids": [
"CWE-22",
"CWE-862"
],
"github_reviewed": true,
"github_reviewed_at": "2026-10-07T18:00:06Z",
"nvd_published_at": "2026-10-06T21:17:17Z",
"severity": "MODERATE"
},
"details": "### Impact\n\nAn authenticated user with access to one TechDocs documentation site could craft a URL able to read documentation belonging to a different entity. This only affects deployments using the external TechDocs builder with an external storage provider (S3, GCS, etc.) and the permission framework enabled. Instances that do not use the permission framework are unaffected, since TechDocs content is visible to all authenticated users by design.\n\n### Patches\n\nPatched in `@backstage/plugin-techdocs-backend` version `2.2.4`\n\n### Workarounds\n\n- None other than upgrading. Deployments that serve TechDocs from local storage are not affected.",
"id": "GHSA-rg9r-hr7g-5gc2",
"modified": "2026-10-07T18:00:06Z",
"published": "2026-10-07T18:00:06Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/backstage/backstage/security/advisories/GHSA-rg9r-hr7g-5gc2"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-106489"
},
{
"type": "WEB",
"url": "https://github.com/backstage/backstage/commit/bf6bbf7326ada7d96d7b2c4ebc4a71546106f311"
},
{
"type": "PACKAGE",
"url": "https://github.com/backstage/backstage"
},
{
"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:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "Backstage: Improper authorization enforcement for TechDocs static content"
}
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.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
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.