# CVE-2026-119417: CakePHP through 5.4.3 Email Header Injection via Bare CR/LF in SmtpTransport and MailTransport


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 30 Oct 2026
- **Updated:** 30 Oct 2026
- **Also known as:** GHSA-xmwp-gcgj-p387, UBUNTU-CVE-2026-119417

## What is CVE-2026-119417?

CVE-2026-119417 is a medium-severity vulnerability in cakephp, published on 30 Oct 2026. 

### Official description

CakePHP 4.5.12, 4.6.5, 5.1.8 through 5.1.10, 5.2.14 through 5.2.15, 5.3.7, and 5.4.0 through 5.4.3 contain an email header injection vulnerability because SmtpTransport and MailTransport strip only CRLF pairs from header values, an incomplete fix for CVE-2026-77634. Attackers controlling custom headers set via Message::setHeaders() or Message::addHeaders() can insert a bare CR or LF to inject headers like Bcc, redirecting or altering outgoing mail.

Weakness: CWE-93 (Improper Neutralization of CRLF Sequences)

## Which versions are affected by CVE-2026-119417?


## How do I fix CVE-2026-119417?

Upgrade to a fixed version.

## Is CVE-2026-119417 being exploited?

There is no known exploitation of CVE-2026-119417 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119417 and fix it if it is affected.

What it is: CVE-2026-119417 is a medium-severity vulnerability in cakephp, published on 30 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119417 in the wild and no public exploit code.

Affected product: cakephp. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-119417/ (Markdown: https://insights.sbomify.com/CVE-2026-119417/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119417
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119417
- OSV: https://osv.dev/vulnerability/CVE-2026-119417

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119417/
Summaries are generated and may contain mistakes; the official description above is the record.