# CVE-2026-45070: Symfony: Email Header Injection via Non-Token Characters in Mime Parameter Names > Attackers can inject arbitrary headers into emails by exploiting unvalidated parameter names in Symfony's MIME component, potentially altering email structure. - **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 14 Jul 2026 - **Updated:** 16 Jul 2026 - **Also known as:** CLSA-2026-1783386119, DEBIAN-CVE-2026-45070, GHSA-vqc8-7275-q272, UBUNTU-CVE-2026-45070 ## What is CVE-2026-45070? CVE-2026-45070 is a medium-severity vulnerability in Sensiolabs Symfony, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Symfony is a PHP framework for web and console applications and a set of reusable PHP components. Prior to 5.4.52, 6.4.40, 7.4.12, and 8.0.12, Symfony\Component\Mime\Header\ParameterizedHeader validates and encodes parameter values but emits parameter names verbatim, allowing a caller that derives a parameter name from untrusted input to include CRLF or other non-token bytes and inject additional headers into rendered structured mail headers such as Content-Type or Content-Disposition. This issue is reported as fixed in versions 5.4.52, 6.4.40, 7.4.12, and 8.0.12. Weakness: CWE-93 (Improper Neutralization of CRLF Sequences) ## Which versions are affected by CVE-2026-45070? 16 open source packages ship an affected version, including symfony/mime and symfony/symfony. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `symfony/mime` | Packagist | All versions | 5.4.52 | | `symfony/mime` | Packagist | All versions | 5.4.52 | | `symfony/mime` | Packagist | From 6.0.0 | 6.4.40 | | `symfony/mime` | Packagist | From 6.0.0 | 6.4.40 | | `symfony/mime` | Packagist | From 7.0.0 | 7.4.12 | | `symfony/mime` | Packagist | From 7.0.0 | 7.4.12 | | `symfony/mime` | Packagist | From 8.0.0 | 8.0.12 | | `symfony/mime` | Packagist | From 8.0.0 | 8.0.12 | | `symfony/symfony` | Packagist | All versions | 5.4.52 | | `symfony/symfony` | Packagist | All versions | 5.4.52 | | `symfony/symfony` | Packagist | From 6.0.0 | 6.4.40 | | `symfony/symfony` | Packagist | From 6.0.0 | 6.4.40 | | `symfony/symfony` | Packagist | From 7.0.0 | 7.4.12 | | `symfony/symfony` | Packagist | From 7.0.0 | 7.4.12 | | `symfony/symfony` | Packagist | From 8.0.0 | 8.0.12 | | `symfony/symfony` | Packagist | From 8.0.0 | 8.0.12 | Products: Sensiolabs Symfony. ## How do I fix CVE-2026-45070? Upgrade symfony/mime to a fixed version for your release line: 5.4.52, 6.4.40, 7.4.12 or 8.0.12. ## Is CVE-2026-45070 being exploited? There is no known exploitation of CVE-2026-45070 in the wild and no public exploit code. ## Other vulnerabilities in Sensiolabs Symfony - [CVE-2019-11325](https://insights.sbomify.com/CVE-2019-11325/): Improper Input Validation in Symfony (critical 9.8) - [CVE-2017-11365](https://insights.sbomify.com/CVE-2017-11365/): Symfony Incorrect Access Control (critical 9.8) - [CVE-2019-10913](https://insights.sbomify.com/CVE-2019-10913/): Invalid HTTP method overrides allow possible XSS or other attacks in Symfony (critical 9.8) - [CVE-2018-11407](https://insights.sbomify.com/CVE-2018-11407/): Symfony Authentication Bypass (critical 9.8) - [CVE-2016-2403](https://insights.sbomify.com/CVE-2016-2403/): Symfony Authentication Bypass (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-45070 and fix it if it is affected. What it is: CVE-2026-45070 is a medium-severity vulnerability in Sensiolabs Symfony, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-45070 in the wild and no public exploit code. Affected packages and fixed versions: - symfony/mime (Packagist): affected all versions; fixed in 5.4.52 - symfony/mime (Packagist): affected all versions; fixed in 5.4.52 - symfony/mime (Packagist): affected from 6.0.0; fixed in 6.4.40 - symfony/mime (Packagist): affected from 6.0.0; fixed in 6.4.40 - symfony/mime (Packagist): affected from 7.0.0; fixed in 7.4.12 - symfony/mime (Packagist): affected from 7.0.0; fixed in 7.4.12 - symfony/mime (Packagist): affected from 8.0.0; fixed in 8.0.12 - symfony/mime (Packagist): affected from 8.0.0; fixed in 8.0.12 - symfony/symfony (Packagist): affected all versions; fixed in 5.4.52 - symfony/symfony (Packagist): affected all versions; fixed in 5.4.52 - symfony/symfony (Packagist): affected from 6.0.0; fixed in 6.4.40 - symfony/symfony (Packagist): affected from 6.0.0; fixed in 6.4.40 Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-45070/ (Markdown: https://insights.sbomify.com/CVE-2026-45070/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-45070 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-45070 - OSV: https://osv.dev/vulnerability/CVE-2026-45070 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-45070/ Summaries are generated and may contain mistakes; the official description above is the record.