Contact us
← Article questionsWhat’s the evidence?

CVEHit Business Advisory by IntegrityLab.ai

What’s the evidence?

Fixed upstream path on a Fastify proxy can be bypassed — CVE-2026-120213: Business Triage

The reported finding

Prefix escape via decoded route parameters

Original advisory →
Required conditions
  • @fastify/http-proxy 9.0.0 through 11.6.5.
  • The route uses a parameterized prefix and rewritePrefix to pin callers to one upstream path.
  • A caller can reach that route.
Reported outcome
  • The plugin substitutes URL-decoded route parameters into rewritePrefix without re-encoding them.
  • A remote caller who does not need an account can reach upstream locations outside the intended prefix.
  • That is a path-restriction bypass.
  • Depending on the upstream service, it can be an authorization bypass in that service.
  • The CVE record also names server-side request forgery: a request sent through the proxy to a place the caller should not reach. That result is limited to what the upstream service allows.
  • The evidence does not establish:
    • Arbitrary-host access.
    • Remote code execution.
    • Full network takeover.

Fix guidance

  • Upgrade to @fastify/http-proxy 11.6.6 or later. No other workaround is named.
  • Release v11.6.6 is the named security release.
  • Edition limits, from the v11.6.6 readme:
    • The package requires Fastify 5.x.
    • Fastify 4.x users are pointed to the 9.x line.
    • The 9.x line is inside the affected range.
    • No fixed 9.x release is named.
  • Version wording:
    • The CVE text says 11.6.6 or later.
    • The advisory patched-version field names 11.6.6.
    • This bundle does not review a later release separately.
  • An update does not show whether earlier access happened.
  • Exploitation records in this bundle:
    • CISA SSVC on Nov 2, 2026 lists exploitation as none.
    • That assessment does not prove that attacks have not occurred.
    • KEV catalog version 2026.11.10, released Nov 10, 2026, has no entry.
    • The CVE record was published Nov 2, 2026, so this snapshot is after disclosure.
    • The catalog file was retrieved Nov 12, 2026.
    • The match method was exact CVE identifier equality. Matching entries: none.
    • No entry in that snapshot does not prove that attacks have not occurred.

What IntegrityLab.ai can check

  • The authorized unauthenticated HTTP check can record a reachable web service and the server name returned in the response.
    • It collects:
      • Response status.
      • Page title.
      • Content length.
      • Server identification.
  • This is a clue for the owner, not a detection of CVE-2026-120213.
    • It does not establish:
      • Use of @fastify/http-proxy.
      • The installed version.
      • Patch status.
    • It does not establish:
      • The prefix setting.
      • The rewritePrefix setting.
    • It does not establish what the service behind the proxy allows.
    • It does not establish whether harm occurred.
    • No validated detection for CVE-2026-120213 was found in the reviewed scanner code or bundled templates.
    • A missing server name does not rule the product out. A front server can hide the service behind it.
    • This check does not establish a private route that is not exposed to that discovery path.
  • Application owner: confirm from internal records:
    • The package.
    • The installed version.
    • The Fastify version group.
    • The route settings.

How to read the score

OpenJS CVSS 3.1: 9.1 (CRITICAL). Use the conditions and update history alongside the score to set your priorities.

Sources and vendor guidance

← Back to article questions

How can we help?

Initial enquiries only. Omit passwords, access tokens, security reports or other sensitive information. We’ll arrange secure sharing if needed.

Privacy & data handling ↗. Submitting this form does not authorise an assessment.

Checking enquiry availability…