NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Composer (PHP)

CVE-2026-45070: Symfony has Email Header Injection via Non-Token Characters in Mime Parameter Names

mediumCVSS 4.0 4.9GHSA-vqc8-7275-q272

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").

Published May 27, 2026

Affected packages

symfony/mime

Ecosystem
Composer (PHP)
Affected
< 5.4.52
Fixed in
5.4.52
Check
composer show symfony/mime

symfony/symfony

Ecosystem
Composer (PHP)
Affected
< 5.4.52
Fixed in
5.4.52
Check
composer show symfony/symfony

symfony/mime

Ecosystem
Composer (PHP)
Affected
>= 6.0.0, < 6.4.40
Fixed in
6.4.40
Check
composer show symfony/mime

symfony/mime

Ecosystem
Composer (PHP)
Affected
>= 7.0.0, < 7.4.12
Fixed in
7.4.12
Check
composer show symfony/mime

symfony/mime

Ecosystem
Composer (PHP)
Affected
>= 8.0.0, < 8.0.12
Fixed in
8.0.12
Check
composer show symfony/mime

symfony/symfony

Ecosystem
Composer (PHP)
Affected
>= 6.0.0, < 6.4.40
Fixed in
6.4.40
Check
composer show symfony/symfony

symfony/symfony

Ecosystem
Composer (PHP)
Affected
>= 7.0.0, < 7.4.12
Fixed in
7.4.12
Check
composer show symfony/symfony

symfony/symfony

Ecosystem
Composer (PHP)
Affected
>= 8.0.0, < 8.0.12
Fixed in
8.0.12
Check
composer show symfony/symfony

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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.

Credited to alexandre-daubois.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More Composer (PHP) vulnerabilities

All Composer (PHP) entries