https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 07:28:25 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-274908 EUVD-2026-274908 https://cve.radiocsirt.org/vuln/euvd-2026-274908 https://cve.radiocsirt.org/vuln/fkie_cve-2026-3419 <p>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.</p> <p>When 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.</p> <p>Impact: An 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.</p> <p>Workarounds: Deploy a WAF rule to protect against this</p> <p>Fix:</p> <p>The fix is available starting with v5.8.1.</p> <p>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.</p> <p>When 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.</p> <p>Impact: An 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.</p> <p>Workarounds: Deploy a WAF rule to protect against this</p> <p>Fix:</p> <p>The fix is available starting with v5.8.1.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-3419 https://cve.radiocsirt.org/vuln/ghsa-573f-x89g-hqp9 <p><strong>Affected:</strong> npm: fastify</p> <p># Description</p> <p>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`.</p> <p>When 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.</p> <p>## Impact</p> <p>An 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.</p> <p>## Workarounds</p> <p>Deploy a WAF rule to protect against this</p> <p>## Fix</p> <p>The fix is available starting with v5.8.1.</p> <p><strong>Affected:</strong> npm: fastify</p> <p># Description</p> <p>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`.</p> <p>When 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.</p> <p>## Impact</p> <p>An 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.</p> <p>## Workarounds</p> <p>Deploy a WAF rule to protect against this</p> <p>## Fix</p> <p>The fix is available starting with v5.8.1.</p> https://cve.radiocsirt.org/vuln/ghsa-573f-x89g-hqp9