{"answers":{"affected":"2 open source packages ship an affected version, including @backstage/plugin-techdocs-backend. It affects 2 products.","exploited":"There is no known exploitation of CVE-2026-106489 in the wild and no public exploit code.","fix":"Upgrade @backstage/plugin-techdocs-backend to 2.2.4 or later.","what":"CVE-2026-106489 is a medium-severity missing authorization vulnerability in Linuxfoundation Backstage, published on 6 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-106489 and fix it if it is affected.\n\nWhat it is: CVE-2026-106489 is a medium-severity missing authorization vulnerability in Linuxfoundation Backstage, published on 6 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-106489 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @backstage/plugin-techdocs-backend (npm): affected all versions; fixed in 2.2.4\n- @backstage/plugin-techdocs-backend (npm): affected all versions; fixed in 2.2.4\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-106489/ (Markdown: https://insights.sbomify.com/CVE-2026-106489/index.md)","id":"CVE-2026-106489","markdown":"https://insights.sbomify.com/CVE-2026-106489/index.md","name":"CVE-2026-106489","record":{"aliases":["GHSA-rg9r-hr7g-5gc2"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Backstage developer portal","requires_auth":"low_privilege","summary":"Authenticated users can read unauthorized TechDocs content via crafted URLs in specific external storage configurations.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"backstage","vendor":"linuxfoundation"},{"product":"backstage\\/plugin-techdocs-backend","vendor":"linuxfoundation"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Backstage is an open framework for building developer portals. Prior to 2.2.4, the @backstage/plugin-techdocs-backend package is affected by improper authorization enforcement for techdocs static content. 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. This issue is fixed in version 2.2.4.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Backstage: Improper authorization enforcement for TechDocs static content","id":"CVE-2026-106489","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":"linuxfoundation:backstage","products":["linuxfoundation:backstage"],"type":"missing_authorization","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Backstage: Improper input validation in TechDocs static content requests","id":"CVE-2026-106490"},"packages":[{"ecosystem":"npm","fixed":["2.2.4"],"introduced":["0"],"last_affected":[],"package":"@backstage/plugin-techdocs-backend","purl":null,"source":"GHSA-rg9r-hr7g-5gc2"},{"ecosystem":"npm","fixed":["2.2.4"],"introduced":["0"],"last_affected":[],"package":"@backstage/plugin-techdocs-backend","purl":"pkg:npm/%40backstage/plugin-techdocs-backend","source":"GHSA-rg9r-hr7g-5gc2"}],"prev":{"headline":"Backstage: Improper authentication in the OIDC provider","id":"CVE-2026-106488"},"products":["backstage","plugin-techdocs-backend"],"published":"2026-10-06","related":[{"cvss_score":9.6,"headline":"Backstage: Sensitive information exposure in Scaffolder","id":"CVE-2026-106501","kev_date_added":null,"published":"2026-10-06"},{"cvss_score":8.8,"headline":"Backstage: Improper validation of TechDocs MkDocs configuration","id":"CVE-2026-106558","kev_date_added":null,"published":"2026-10-07"},{"cvss_score":8.8,"headline":"Backstage: Improper input validation in TechDocs MkDocs configuration","id":"CVE-2026-88064","kev_date_added":null,"published":"2026-09-16"},{"cvss_score":8.5,"headline":"Backstage: Improper input validation in Sentry scaffolder actions","id":"CVE-2026-106459","kev_date_added":null,"published":"2026-10-06"},{"cvss_score":8.5,"headline":"Backstage: Improper filesystem validation in Bitbucket pull-request scaffolder actions","id":"CVE-2026-106486","kev_date_added":null,"published":"2026-10-06"},{"cvss_score":8.5,"headline":"Backstage: Improper task state validation in Scaffolder backend","id":"CVE-2026-106500","kev_date_added":null,"published":"2026-10-06"},{"cvss_score":8.5,"headline":"Path Traversal in @backstage/plugin-scaffolder-backend","id":"CVE-2021-43783","kev_date_added":null,"published":"2021-11-29"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-07","vendors":["@backstage","backstage"]},"summary":"Authenticated users can read unauthorized TechDocs content via crafted URLs in specific external storage configurations.","url":"https://insights.sbomify.com/CVE-2026-106489/"}