symfony/mime
Affected
- introduced
0, fixed5.4.52(ecosystem)
Fixed versions
5.4.52
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2026-45070
Symfony has Email Header Injection via Non-Token Characters in Mime Parameter Names
Description
Symfony\Component\Mime\Header\ParameterizedHeader (and the related parameter handling reachable from Symfony\Component\Mime\Header\Headers) is responsible for serializing structured headers such as Content-Type and Content-Disposition, which carry key=value parameters (e.g. Content-Disposition: attachment; filename="x").
RFC 2045 / RFC 5322 require parameter *names* to be tokens: a restricted ASCII subset that excludes whitespace, CR/LF, and the tspecials set. Symfony's parameter handling validates and properly encodes parameter *values*, but does not validate parameter *names*: the supplied name is emitted verbatim into the serialized header.
A caller that derives a parameter name from untrusted input, e.g. an application that lets a user influence a Content-Disposition parameter name, can include \r\n or other non-token bytes inside the name, terminating the current header and injecting additional headers in the rendered message. This is the classic CRLF / header-injection primitive applied to the parameter-name slot.
Resolution
ParameterizedHeader now rejects parameter names that contain bytes outside the RFC token character class.
The patch for this issue is available here for branch 5.4.
Credits
Symfony would like to thank Fabian Fleischer for reporting the issue and Alexandre Daubois for fixing it.
Medium Basis: The source's own band: MODERATE
0, fixed 5.4.52 (ecosystem)5.4.52
The export has no generic command for this ecosystem.
0, fixed 5.4.52 (ecosystem)5.4.52
The export has no generic command for this ecosystem.
6.0.0, fixed 6.4.40 (ecosystem)6.4.40
The export has no generic command for this ecosystem.
7.0.0, fixed 7.4.12 (ecosystem)7.4.12
The export has no generic command for this ecosystem.
8.0.0, fixed 8.0.12 (ecosystem)8.0.12
The export has no generic command for this ecosystem.
6.0.0, fixed 6.4.40 (ecosystem)6.4.40
The export has no generic command for this ecosystem.
7.0.0, fixed 7.4.12 (ecosystem)7.4.12
The export has no generic command for this ecosystem.
8.0.0, fixed 8.0.12 (ecosystem)8.0.12
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0