Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA GitHub_M

CVE-2026-106493: Backstage: Cloud storage catalog locations may cross configured storage boundaries

MediumCVSS 4.1 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 16/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.27% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: backstage backstage 1.54.6.

Low priority for now. Upgrade to backstage backstage 1.54.6 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Backstage is an open framework for building developer portals. Prior to 1.54.6, cloud storage catalog providers did not sufficiently validate object paths. A principal able to create or rename objects in a configured Azure Blob Storage or AWS S3 catalog source could cause catalog descriptors to be read from outside the intended storage boundary, limited to locations reachable with the backend's configured credentials. This issue is fixed in 1.54.6.

Published
Oct 6, 2026
Updated
Oct 22, 2026
EPSS
0.2% · 20th percentile

Report tools

JSON

Action score

16

Monitor

Low priority for now.

CVSS
16 / 40 · 4.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
4.1
CNA · GitHub_M
3.0
1.1 point gap

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:N/A:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-106493

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxfoundationbackstage
linuxfoundationbackstage/backend-defaults
linuxfoundationbackstage/plugin-catalog-backend-module-aws
linuxfoundationbackstage/plugin-catalog-backend-module-azure

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • @backstage plugin-catalog-backend-module-aws

    • < 0.4.27affected
  • @backstage plugin-catalog-backend-module-azure

    • < 0.17.8, < 0.3.21affected
  • backstage backstage

    • < 1.54.6affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
npm@backstage/backend-defaultsbefore 0.17.80.17.8
npm@backstage/plugin-catalog-backend-module-awsbefore 0.4.270.4.27
npm@backstage/plugin-catalog-backend-module-azurebefore 0.3.210.3.21

Other highest-scoring records for the same primary product.

  • CVE-2023-35926Insecure sandbox in Backstage Scaffolder plugin
    40Plan
  • CVE-2026-25153@backstage/plugin-techdocs-node vulnerable to arbitrary code execution via MkDocs hooks
    35Monitor
  • CVE-2021-43783Path Traversal in @backstage/plugin-scaffolder-backend
    34Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2026-32235Mar 12, 2026 · @backstage/plugin-auth-backend: OAuth redirect URI allowlist bypass
    18Monitor
  • ← EarlierCVE-2026-32236Mar 12, 2026 · @backstage/plugin-auth-backend: SSRF in experimental CIMD metadata fetch
    6Monitor
  • Later →CVE-2026-106556Oct 7, 2026 · Backstage: Configuration bypass in TechDocs mkdocs.yml sanitization
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
backstage backstage1.54.6 · descriptionVendor (CNA)
npm:@backstage/backend-defaults0.17.8Package registry (OSV)
npm:@backstage/plugin-catalog-backend-module-aws0.4.27Package registry (OSV)
npm:@backstage/plugin-catalog-backend-module-azure0.3.21Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. Fix recordedsame day
  3. TodayNov 13, 2026+38 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-25152249 days apart@backstage/plugin-techdocs-node vulnerable to possible Path Traversal in TechDocs Local Generator
    26Monitor

Not on record for this CVE: researcher credit · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • Administrator privileges are required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
none
Availability
none

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Changed
Confidentiality impact
Low
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N

nvd-primary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const file = path.join(ROOT, req.query.name);res.sendFile(file);

Fixed

ts
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) {  return res.sendStatus(400);}res.sendFile(file);

Change log

  1. CVSS3 → 4.1
  2. Severitylow → medium
  3. SSVC exploitation— → none
  4. Exploit maturity— → none
  5. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records