{"answers":{"affected":"2 open source packages ship an affected version, including fastify. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-3419 in the wild and no public exploit code.","fix":"Upgrade fastify to 5.8.1 or later.","what":"CVE-2026-3419 is a medium-severity vulnerability in fastify, published on 6 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-3419 and fix it if it is affected.\n\nWhat it is: CVE-2026-3419 is a medium-severity vulnerability in fastify, published on 6 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-3419 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- fastify (npm): affected from 5.7.2; fixed in 5.8.1\n- fastify (npm): affected from 5.7.2; fixed in 5.8.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-3419/ (Markdown: https://insights.sbomify.com/CVE-2026-3419/index.md)","id":"CVE-2026-3419","markdown":"https://insights.sbomify.com/CVE-2026-3419/index.md","name":"CVE-2026-3419","record":{"aliases":["GHSA-573f-x89g-hqp9"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Fastify web framework","requires_auth":"none","summary":"Attackers can bypass Content-Type validation in Fastify by sending malformed headers, potentially routing requests to unintended parsers.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"openjs","cpe":[{"product":"fastify","vendor":"fastify"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-185","name":"Incorrect Regular Expression"}],"description":"Fastify incorrectly accepts malformed `Content-Type` headers containing trailing characters after the subtype token, in violation of RFC 9110 §8.3.1(https://httpwg.org/specs/rfc9110.html#field.content-type). For example, a request sent with Content-Type: application/json garbage passes validation and is processed normally, rather than being rejected with 415 Unsupported Media Type.\n\nWhen regex-based content-type parsers are in use (a documented Fastify feature), the malformed value is matched against registered parsers using the full string including the trailing garbage. This means a request with an invalid content-type may be routed to and processed by a parser it should never have reached.\n\nImpact:\nAn attacker can send requests with RFC-invalid Content-Type headers that bypass validity checks, reach content-type parser matching, and be processed by the server. Requests that should be rejected at the validation stage are instead handled as if the content-type were valid.\n\nWorkarounds:\nDeploy a WAF rule to protect against this\n\nFix:\n\nThe fix is available starting with v5.8.1.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Fastify's Missing End Anchor in \"subtypeNameReg\" Allows Malformed Content-Types to Pass Validation","id":"CVE-2026-3419","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":2,"n_references":6,"next":{"headline":"e-Excellence｜U-Office Force - Insecure Deserialization","id":"CVE-2026-3422"},"packages":[{"ecosystem":"npm","fixed":["5.8.1"],"introduced":["5.7.2"],"last_affected":[],"package":"fastify","purl":null,"source":"GHSA-573f-x89g-hqp9"},{"ecosystem":"npm","fixed":["5.8.1"],"introduced":["5.7.2"],"last_affected":[],"package":"fastify","purl":"pkg:npm/fastify","source":"GHSA-573f-x89g-hqp9"}],"prev":{"headline":"Arbitrary File Upload via System REST API in Multiple WSO2 Products Allows Remote Code Execution","id":"CVE-2026-3418"},"products":["fastify"],"published":"2026-03-06","related":[{"cvss_score":8.1,"headline":"fastify vulnerable to request body replacement via an async validation result collision","id":"CVE-2026-84504","kev_date_added":null,"published":"2026-09-04"},{"cvss_score":7.5,"headline":"fastify vulnerable to authentication bypass via malformed URLs reaching encapsulated not-found handlers","id":"CVE-2026-76169","kev_date_added":null,"published":"2026-09-04"},{"cvss_score":7.5,"headline":"fastify vulnerable to header validation bypass via incomplete schema case normalization","id":"CVE-2026-84428","kev_date_added":null,"published":"2026-09-04"},{"cvss_score":7.5,"headline":"fastify vulnerable to request validation bypass via skipped boolean false schemas","id":"CVE-2026-84469","kev_date_added":null,"published":"2026-09-04"},{"cvss_score":7.5,"headline":"fastify vulnerable to Body Schema Validation Bypass via Leading Space in Content-Type Header","id":"CVE-2026-33806","kev_date_added":null,"published":"2026-04-15"},{"cvss_score":7.5,"headline":"Fastify's Content-Type header tab character allows body validation bypass","id":"CVE-2026-25223","kev_date_added":null,"published":"2026-02-03"},{"cvss_score":7.5,"headline":"Fastify vulnerable to invalid content-type parsing, which could lead to validation bypass","id":"CVE-2025-32442","kev_date_added":null,"published":"2025-04-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-09","vendors":["fastify"]},"summary":"Attackers can bypass Content-Type validation in Fastify by sending malformed headers, potentially routing requests to unintended parsers.","url":"https://insights.sbomify.com/CVE-2026-3419/"}