Skip to main content
No exploitation reportedFix available

CVE-2025-32442

No exploitation reported by the sources we read.

  • Published2025-04-18
  • Fixed in5.8.5 · 5.3.2 · 4.29.1
  • WeaknessCWE-1287

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

Fastify is a fast and low overhead web framework, for Node.js. In versions 5.0.0 to 5.3.0 as well as version 4.29.0, applications that specify different validation strategies for different content types have a possibility to bypass validation by providing a _slightly altered_ content type such as with different casing or altered whitespacing before `;`. This was patched in v5.3.1, but the initial patch did not cover all problems. This has been fully patched in v5.3.2 and v4.29.1. A workaround involves not specifying individual content types in the schema.

Timeline

dates in UTC
  1. 2025-04-1816:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2025-32442?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2025-32442?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

OSV · NVD
Fastify
BranchAffectedFixed in
5.x≥ 5.3.2, < 5.8.55.8.5
5.x≥ 5.0.0, < 5.3.25.3.2
4.29≥ 4.29.0, < 4.29.14.29.1
4.29= 4.29.0no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

  • CVE-2025-32442 Red Hat Product Security

    Fastify: Fastify vulnerable to invalid content-type parsing, which could lead to validation bypass

Full record on NVD

Fix

  1. Update Fastify to 5.8.5 · 5.3.2 · 4.29.1

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • NVDCVE recordread 2026-10-23
  • CISA-ADPSSVC decisionnone2025-04-21
  • OpenCVESSVC decisionnone—
  • CNACVSS 3.17.5read 2026-10-23
  • CNAweakness (CWE)CWE-1287read 2026-10-23
  • FIRST EPSSEPSS score0.7 %2026-10-23
  • OSVaffected packages—

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Published
2025-04-18
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2025-32442?

Fastify is a fast and low overhead web framework, for Node.js. In versions 5.0.0 to 5.3.0 as well as version 4.29.0, applications that specify different validation strategies for different content types have a possibility to bypass validation by providing a _slightly altered_ content type such as with different casing or altered whitespacing before `;`. This was patched in v5.3.1, but the initial patch did not cover all problems. This has been fully patched in v5.3.2 and v4.29.1. A workaround involves not specifying individual content types in the schema.

Is CVE-2025-32442 actively exploited?

Active exploitation of CVE-2025-32442 has not been confirmed. Its EPSS score was 0.7% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2025-32442?

CVE-2025-32442 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N.

Running fastify? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month