Contact us
← CVEHit Business AdvisoryFastify HTTP proxy path bypass — CVE-2026-120213: Business Triage

CVEHit Business Advisory by IntegrityLab.ai

Published

Fixed upstream path on a Fastify proxy can be bypassed — CVE-2026-120213: Business Triage9.1/10CRITICAL · CVSS 3.1OpenJSFix available11.6.6 for Fastify 5.xCISA assessmentCVE.org sourceNo KEVChecked Nov 11, 2026

Update affected Fastify 5.x apps to @fastify/http-proxy 11.6.6 or later, and set a migration decision for Fastify 4.x. Research: primary sources retrieved 2026-11-12.

Check these three things.

  1. Application owner: confirm Fastify 5.x apps use @fastify/http-proxy 11.6.6 or later.
    Version and Fastify line
    • Confirm the installed package is @fastify/http-proxy.
    • A Fastify app without this package is outside this advisory.
    • Use the version that is running, not only the version the project requests.
    • Affected releases are 9.0.0 through 11.6.5.
    • Releases before 9.0.0 are not in the affected range.
    • The maintainers state there is no workaround other than upgrading.
    • An affected version needs the upgrade even when the path-limit settings are not in use.
    • Release 11.6.6 requires Fastify 5.x.
    • The v11.6.6 readme points Fastify 4.x users to the 9.x line.
    • That 9.x line is inside the affected range.
    • No fixed 9.x release is named.
    • The CVE text says 11.6.6 or later. The advisory patched-version field names 11.6.6.
    • Record:
      • Application.
      • Installed package version.
      • Fastify version.
      • Source of the record.
      • Date checked.
  2. Application owner: check whether a reachable proxy route combines values from the request address with a fixed upstream path limit.
    Path limit and reachability
    • The upstream is the service the proxy forwards requests to.
    • This exposure needs both settings that keep callers on one upstream path.
      • prefix includes a value taken from the route. The advisory calls that a parameterized prefix.
      • rewritePrefix is the upstream path callers should stay on.
    • A caller must be able to reach that route.
      • The CVE record describes a remote caller who does not need an account.
      • A sign-in page does not prove the route is vulnerable.
      • A sign-in page does not prove the route is safe.
      • A login requirement is not a listed workaround.
    • An app that does not use this pair is outside this exposure.
    • The package can need the upgrade even so.
    • @fastify/http-proxy 11.6.6 or later on Fastify 5.x rules out current exposure, including where those settings remain.
    • That fix does not settle earlier exposure or actual harm.
    • Current settings do not show the settings used before an upgrade.
    • Record:
      • Whether prefix includes a route value.
      • Whether rewritePrefix is set.
      • Who can reach the route.
      • Source of the record.
      • Date checked.
  3. Security owner: review records on the service behind the proxy for access beyond the intended path or unexpected changes.
    What the records can show
    • Requests outside the intended path.
    • Unexpected changes to data or settings on that service.
    • Fastify request logs, only if logging was already on.
      • Fastify's logging documentation says logging is off by default.
      • It cannot be turned on while the app runs.
      • When logging is on, Fastify adds an ID to each request. That ID helps only where a log exists.
    • A missing Fastify log leaves only that evidence unresolved.
    • If records for the service behind the proxy are missing, actual harm stays unresolved.
    • A clean record is not proof that access did not happen.
    • Record:
      • Records reviewed.
      • Source of the records.
      • Period covered.
      • Date reviewed.

Do Now

  • Application owner: update each affected Fastify 5.x app to @fastify/http-proxy 11.6.6 or later.
    Proof the update is done
    • The maintainers state there is no workaround other than upgrading.
    • Release 11.6.6 requires Fastify 5.x.
    • The CVE text says 11.6.6 or later. The advisory patched-version field names 11.6.6.
    • Confirm the version that is running after the update.
    • This update does not show whether earlier access happened.
    • Record:
      • Application.
      • Installed plugin version.
      • Fastify version.
      • Source of the record.
      • Date checked.
  • Application owner: choose a migration path for affected Fastify 4.x apps because no compatible fixed release is established.
    What the decision must cover
    • Release 11.6.6 requires Fastify 5.x.
    • The v11.6.6 readme points Fastify 4.x users to the 9.x line.
    • The 9.x line is inside the affected range.
    • No fixed 9.x release is named.
    • No patched release for Fastify 4.x is named.
    • The maintainers list no workaround other than upgrading.
    • Record:
      • Application.
      • Fastify version.
      • Installed plugin version.
      • Decision.
      • Date decided.
  • Security owner: start response if records on the service behind the proxy show access outside the intended path or unexpected changes.
    When to escalate
    • Include apps that ran 9.0.0 through 11.6.5 with the fixed-path setting, including apps already updated.
    • An update does not show that earlier access did not happen.
    • Act even if this CVE is not established as the cause.
    • Fastify logging is off by default and cannot be turned on while the app runs.
    • A missing Fastify log leaves only that evidence unresolved. Review the records that exist for the service behind the proxy.
    • A clean record is not proof that access did not happen.
    • Record:
      • Records reviewed.
      • Source of the records.
      • Period covered.
      • Date reviewed.

Do Next

  • Application owner: decide whether to turn on Fastify request logging before proxy apps start.
    What to weigh
    • Fastify's logging documentation says logging is off by default.
    • It cannot be turned on while the app runs.
    • Without request records, later questions about proxy use may stay unresolved.
    • Logging does not identify this CVE. It only keeps request records.
    • When logging is on, Fastify adds an ID to each request.
    • Record:
      • Decision.
      • Applications covered.
      • Date decided.

Check your own records.

  • Use your approved AI tool.
  • Require evidence. Flag unknowns.

Read the prompt

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

Need an independent review of your public exposure?

See IntegrityLab.ai →

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…