CVE-2026-3419

{"id": "CVE-2026-3419", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "ce714d77-add3-4f53-aff5-83d477b104bb", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 1.4, "exploitabilityScore": 3.9}]}, "published": "2026-03-06T18:16:22.213", "references": [{"url": "https://cna.openjsf.org/security-advisories.html", "tags": ["Vendor Advisory"], "source": "ce714d77-add3-4f53-aff5-83d477b104bb"}, {"url": "https://github.com/advisories/GHSA-573f-x89g-hqp9", "tags": ["Patch", "Vendor Advisory"], "source": "ce714d77-add3-4f53-aff5-83d477b104bb"}, {"url": "https://github.com/fastify/fastify/commit/67f6c9b32cb3623d3c9470cc17ed830dd2f083d7", "tags": ["Patch"], "source": "ce714d77-add3-4f53-aff5-83d477b104bb"}, {"url": "https://github.com/fastify/fastify/security/advisories/GHSA-573f-x89g-hqp9", "tags": ["Vendor Advisory"], "source": "ce714d77-add3-4f53-aff5-83d477b104bb"}, {"url": "https://httpwg.org/specs/rfc9110.html#field.content-type", "tags": ["Technical Description"], "source": "ce714d77-add3-4f53-aff5-83d477b104bb"}, {"url": "https://www.cve.org/CVERecord?id=CVE-2026-3419", "tags": ["VDB Entry"], "source": "ce714d77-add3-4f53-aff5-83d477b104bb"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Secondary", "source": "ce714d77-add3-4f53-aff5-83d477b104bb", "description": [{"lang": "en", "value": "CWE-185"}]}], "descriptions": [{"lang": "en", "value": "Fastify incorrectly accepts malformed `Content-Type` headers containing trailing characters after the subtype token, in violation of RFC 9110 \u00a78.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."}, {"lang": "es", "value": "Fastify acepta incorrectamente encabezados `Content-Type` malformados que contienen caracteres adicionales despu\u00e9s del token de subtipo, en violaci\u00f3n de la RFC 9110 \u00a78.3.1(https://httpwg.org/specs/rfc9110.html#field.content-type). Por ejemplo, una solicitud enviada con Content-Type: application/json garbage pasa la validaci\u00f3n y se procesa normalmente, en lugar de ser rechazada con 415 Unsupported Media Type.\n\nCuando se utilizan analizadores de tipo de contenido basados en expresiones regulares (regex) (una caracter\u00edstica documentada de Fastify), el valor malformado se compara con los analizadores registrados utilizando la cadena completa, incluidos los caracteres adicionales. Esto significa que una solicitud con un tipo de contenido no v\u00e1lido puede ser enrutada y procesada por un analizador al que nunca deber\u00eda haber llegado.\n\nImpacto:\nUn atacante puede enviar solicitudes con encabezados Content-Type no v\u00e1lidos seg\u00fan la RFC que eluden las comprobaciones de validez, llegan a la coincidencia del analizador de tipo de contenido y son procesadas por el servidor. Las solicitudes que deber\u00edan ser rechazadas en la etapa de validaci\u00f3n son, en cambio, manejadas como si el tipo de contenido fuera v\u00e1lido.\n\nSoluciones provisionales:\nImplementar una regla de WAF para protegerse contra esto\n\nSoluci\u00f3n:\n\nLa soluci\u00f3n est\u00e1 disponible a partir de la v5.8.1."}], "lastModified": "2026-03-18T19:11:46.967", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:fastify:fastify:*:*:*:*:*:node.js:*:*", "vulnerable": true, "matchCriteriaId": "9CAD5359-5175-4ED4-934C-F40C1C0C2EE8", "versionEndExcluding": "5.8.1", "versionStartIncluding": "5.7.2"}], "operator": "OR"}]}], "sourceIdentifier": "ce714d77-add3-4f53-aff5-83d477b104bb"}