Contact us
← Article questionsWhat should we do?

CVEHit Business Advisory by IntegrityLab.ai

What should we do?

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

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.

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