Contact us
← Article questionsDoes this affect us?

CVEHit Business Advisory by IntegrityLab.ai

Does this affect us?

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

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.

← 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…