← Back to results
Vulnerability record · public intelligence
CVE-2026-106491
MEDIUM

Backstage: Improper input validation in proxy-backend

Published Oct 6, 2026 · Updated Oct 24, 2026 · Also known as GHSA-9ghw-48h5-v2w5

Severity · CVSSMEDIUM · 6.4
Known exploitationNot listed
EPSS / likelihood0.27%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Oct 24, 2026

Backstage: Improper input validation in proxy-backend

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

An authenticated Backstage user could craft a request URL that causes the proxy-backend to forward the request to a path outside the configured base path on the target server. This is limited to target servers already configured as proxy endpoints and requires Backstage authentication by default.

Potential impact

An authenticated Backstage user could craft a request URL that causes the proxy-backend to forward the request to a path outside the configured base path on the target server. This is limited to target servers already configured as proxy endpoints and requires Backstage authentication by default.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

CVENVDEPSSGHSA
SSVC priority
LOW
Confidence
Not available
Aliases
GHSA-9ghw-48h5-v2w5

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. Security advisory ↗
  2. Patch commit ↗
  3. Source repository ↗

Record history

Published Oct 6, 2026 · Last refreshed Oct 24, 2026