How severe is CVE-2026-106492?

CVE-2026-106492 has a CVSS score of 7.6/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2026-106492?

CVE-2026-106492 affects the following packages: @backstage/backend-defaults (npm). Ecosystems affected: npm.

How do I fix CVE-2026-106492?

Update @backstage/backend-defaults to 0.17.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-106492 is resolved across your whole dependency graph.

How do I detect CVE-2026-106492 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @backstage/backend-defaults, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-106492 if there is no patch (or I can't update yet)?

Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Is CVE-2026-106492 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-106492 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-106492?

CVE-2026-106492 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 14th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-106492?

CVE-2026-106492 is classified as Improper Privilege Management (CWE-269), CWE-863 (CWE-863). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-106492 published, and has it been updated?

CVE-2026-106492 was published on October 6, 2026 and was last updated on October 21, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

HIGH severity

CVE-2026-106492 — @backstage/backend-defaul…

HIGHFix: backstage/backstage@4034624

CVE-2026-106492 is a high-severity (CVSS 7.6) Improper Privilege Management vulnerability in @backstage/backend-defaults. A fix is available for @backstage/backend-defaults — see the affected versions and patch details below.

Backstage: Improper preservation of access restrictions during service credential delegation

Also known asGHSA-cq7v-rfgc-5c7v

Published

Oct 6, 2026

Updated

Oct 21, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 21, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-106492.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs14th percentile — riskier than 14% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2026-106492 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 394,415 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

📦@backstage/backend-defaults

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

Impact

An external service credential configured with access restrictions (e.g., read-only) could bypass those restrictions by routing requests through plugin delegation paths. This could allow a restricted service to perform operations beyond its intended scope, including write operations on plugins it was restricted to read-only access for.

Patches

Patched in @backstage/backend-defaults version 0.17.8

Workarounds

If you're unable to upgrade immediately:

If practical, replace restricted credentials with separate, purpose-specific unrestricted credentials scoped to trusted consumers.
Restrict network-level access to Backstage backend API endpoints to trusted callers only.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@backstage/backend-defaults`	all versions	0.17.8`npm install @backstage/backend-defaults@0.17.8`

Affected Products

2 products · 4 configurations

Application

backstagelinuxfoundation

≥ 1.50.0 && < 1.54.6

range

Application

backstage\/backend-defaultslinuxfoundation

≥ 0.17.0 && < 0.17.8

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @backstage/backend-defaults, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @backstage/backend-defaults to 0.17.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-106492 is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Red Hat rates this flaw as having an Important severity because an authenticated service token with restricted privileges can evade authorization boundaries to execute unauthorized write operations across backend plugins. In environments running Red Hat Developer Hub or the Ansible Automation Platform, internal…

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Source: Red Hat security advisory for CVE-2026-106492 (CC BY 4.0)

Frequently Asked Questions

### Impact An external service credential configured with access restrictions (e.g., read-only) could bypass those restrictions by routing requests through plugin delegation paths. This could allow a restricted service to perform operations beyond its intended scope, including write operations on plugins it was restricted to read-only access for. ### Patches Patched in `@backstage/backend-defaults` version `0.17.8` ### Workarounds If you're unable to upgrade immediately: - If practical, replace restricted credentials with separate, purpose-specific unrestricted credentials scoped to trus