CVE Intelligence
Medium File handling

CVE-2026-115923 — Backstage catalog rules can be bypassed for URL locations using encoded path segments

Backstage is an open framework for building developer portals. Prior to 3.9.2 and from 4.0.0 until 4.0.2, DefaultCatalogRulesEnforcer in @backstage/plugin-catalog-backend compares the raw location.target URL against catalog.rules, while URL readers canonicalize the same URL before fetching it. An authenticated user with catalog.location.create permission can use percent-encoded path segments to make an untrusted URL match a trusted location pattern even though the canonical URL resolves outside that scope. This admits entity content from an untrusted source as trusted, while further downstream consequences depend on deployment configuration. This issue is fixed in versions 3.9.2 and 4.0.2.

Published Oct 26, 2026 · Updated Oct 26, 2026 · Sources: CVE Program (cve.org) e CISA ADP, NIST National Vulnerability Database · CNA: GitHub_M

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
—
No EPSS score.
Affects
@backstage
Backstage
CVSS base
6.5
Medium · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (@backstage Backstage).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes matching the vulnerability class (file handling), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
@backstage Backstage version < 3.9.2version >= 4.0.0, < 4.0.2 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

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

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
6.5 CVSS 3.1 Medium 2.8 3.6 security-advisories@github.com via NIST National Vulnerability Database
6.5 CVSS 3.1 Medium — — GitHub_M via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N (score shown at the top: security-advisories@github.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-22 · Path Traversal

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Monitor file creation in web directories and paths with traversal sequences (../).
web/proxy/WAF logsnetwork IDS/IPSfile integrity (FIM)endpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Source status changed · Published → Awaiting Analysis
    Oct 26, 2026 · NIST National Vulnerability Database
  • Record published
    Oct 26, 2026
  • CVSS changed · 6.5
    Oct 26, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Published
    Oct 26, 2026 · CVE Program (cve.org) e CISA ADP
  • Record created in this database
    Oct 26, 2026 · CVE Program (cve.org) e CISA ADP
  • CVE published
    Oct 26, 2026 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 26, 2026 – Oct 26, 2026

References

5 on the record

Elsewhere on this site

@backstage
every CVE for this vendor
File handling
same class
CWE-22
other pages naming this weakness

Related CVEs (same products)

  • Medium CVE-2026-106495 Backstage: Improper access control in backend action invocation 14d
  • High CVE-2026-106557 Backstage: Improper input validation in TechDocs Markdown extension configuration 19d
  • Medium CVE-2026-106563 Backstage: Improper entity validation in deprecated Kubernetes services endpoint 19d
  • Medium CVE-2026-106562 Backstage: Incorrect authorization in search engine permission filtering 19d
  • Medium CVE-2026-106559 Backstage: Improper input validation in Confluence to Markdown scaffolder module 19d
  • Medium CVE-2026-106560 Backstage: Improper repository path validation in a Scaffolder backend module 19d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No FIRST EPSS score.
  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-115923 is "Backstage catalog rules can be bypassed for URL locations using encoded path segments", rated Medium. It affects Backstage (@backstage); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.5 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.