Advisory record · GHSA-2qh5-382h-3jpc

CakePHP: SmtpTransport vulnerable to CRLF header injection

CVSS 8.2 HighEPSS 0.0045 · 39th percentile

Published by the GitHub Advisory Database at 8 Sept 2026, 20:56 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
cakephp/cakephpPackagist>=4.5.0, <4.5.12 || >=4.6.0, <4.6.5 || >=5.0.0, <5.1.9 || >=5.2.0, <5.2.14 || >=5.3.0, <5.3.74.5.12, 4.6.5, 5.1.9, 5.2.14, 5.3.7
Identifiers
GHSA-2qh5-382h-3jpc · CVE-2026-119417 · CVE-2026-77634 · PKSA-rdvp-7sns-1dvh
Weakness (CWE)
CWE-93
Published
8 Sept 2026
Updated
31 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

CakePHP's SmtpTransport in cakephp/cakephp versions 4.5.0 before 4.5.12, 4.6.0 before 4.6.5, 5.0.0 before 5.1.9, 5.2.0 before 5.2.14, and 5.3.0 before 5.3.7 does not replace CRLF bytes in custom mail headers added with Message::setHeaders() or addHeaders(). If an application puts user-controlled data into message headers without stripping CRLF bytes, an attacker may be able to inject additional email headers. Upgrade to 4.5.12, 4.6.5, 5.1.9, 5.2.14, or 5.3.7, matching your major and minor version; until then, strip CRLF bytes from header values before setting them.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.2 High 4.0 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0045, the 39th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 13:53 UTC First seen by agentprime
  2. 31 Oct 2026, 13:53 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.