Quick answers
- Is CVE-2026-106512 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-106512 being exploited in the wild.
- How severe is CVE-2026-106512?
- Informational severity, published 6 October 2026.
- Which products and versions are affected?
- Cakephp Versions prior to fix for CVE-2026-106512.
- Is there a fix for CVE-2026-106512?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-106512 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-106512?
- Check whether you run Cakephp at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The CakeResponse::download() method in lib/Cake/Network/CakeResponse.php directly interpolates user-supplied filenames into the Content-Disposition header without sanitization. Two attack vectors exist: CR/LF characters cause PHP to drop the header entirely, serving the response body with its original Content-Type inline in the browser (stored XSS), and double-quotes terminate the quoted-string prematurely, allowing injection of additional Content-Disposition parameters. The vulnerability requires authentication to upload a crafted filename and affects any other authenticated user viewing the page with the malicious attachment.
Affected products
- CakePHP CakePHP Versions prior to fix for CVE-2026-106512
Timeline
- 2026-10-06: disclosed