high Patched

CakePHP: SmtpTransport vulnerable to CRLF header injection

CVE-2026-119417 · CVE-2026-77634 · GHSA-2qh5-382h-3jpc · published 8 Sept 2026

How serious is it

  • Severity: high.
  • No exploit prediction (EPSS) score yet.
  • Not on the CISA list of exploited vulnerabilities.
  • No public exploit in Exploit-DB.

Is your app affected by CVE-2026-119417?

Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.

Who is affected

  • cakephp/cakephp (Packagist) >= 4.5.0, < 4.5.12
  • cakephp/cakephp (Packagist) >= 4.6.0, < 4.6.5
  • cakephp/cakephp (Packagist) >= 5.0.0, < 5.1.9
  • cakephp/cakephp (Packagist) >= 5.2.0, < 5.2.14
  • cakephp/cakephp (Packagist) >= 5.3.0, < 5.3.7

How to check

  1. Run composer show cakephp/cakephp in your project to see the installed version, including copies pulled in by other packages.
  2. Or paste your lockfile into the checker: it lists every package with a known vulnerability, this one included.

How to fix

Copies a prompt for Claude Code, Cursor or Codex: it checks your lockfiles for this and upgrades it.
  1. On >= 4.5.0, < 4.5.12: Upgrade cakephp/cakephp to 4.5.12 or later, commit the lockfile and redeploy.
  2. On >= 4.6.0, < 4.6.5: Upgrade cakephp/cakephp to 4.6.5 or later, commit the lockfile and redeploy.
  3. On >= 5.0.0, < 5.1.9: Upgrade cakephp/cakephp to 5.1.9 or later, commit the lockfile and redeploy.
  4. On >= 5.2.0, < 5.2.14: Upgrade cakephp/cakephp to 5.2.14 or later, commit the lockfile and redeploy.
  5. On >= 5.3.0, < 5.3.7: Upgrade cakephp/cakephp to 5.3.7 or later, commit the lockfile and redeploy.
  6. If a vulnerable version was live, check your logs and rotate the secrets that server could read.

The advisory

### Impact Custom mail headers added with `Message::setHeaders()` or `addHeaders()` do not have CRLF replaced allowing header injection if user controlled data is added to message headers without stripping CRLF bytes. ### Patches 5.3.7, 5.2.14, 5.1.9, 4.6.5, 4.5.12 contain fixes for this issue. ### Workarounds You can strip CRLF bytes from email header values before setting header values.

Check your whole app

Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.

References

Merged from OSV. Last updated 1 Nov 2026. All vulnerabilities · RSS · JSON

Get alerts for new exploited vulnerabilities