caddyserver · Caddy · published 2026-06-23
CVE-2026-45135Caddy: Unsafe Unicode Handling in FastCGI splitPos Allows Execution of Non-PHP Files
This month Public proof-of-concept exists (SSVC exploitation: poc).
CVE-2026-45135 has a public proof-of-concept exploit, but no confirmed exploitation in the wild. EPSS estimates a 0.7% chance of exploitation in the next 30 days, higher than 53% of all CVEs. This Caddy vulnerability: CVSS 8.1 (v3.1), a successful attack gives total control of the component. Fixed upstream in Caddy 2.11.3. Patch in your normal monthly cycle.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Caddy 2.11.3.
Patch events
Web serverCaddy
Caddy security release: 2.11.3
Upgrade to
2.11.3Why: CVE-2026-45135: Public proof-of-concept exists (SSVC exploitation: poc).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.7% (53th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 8.1 (v3.1)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H | CNA / CISA ADP |
| SSVC exploitation | poc | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Affected versions (from the CVE record)#
- caddyserver caddy
>= 2.7.0, < 2.11.3(affected)
Description (from the CVE record)#
Caddy is an extensible server platform that uses TLS by default. From 2.7.0 until 2.11.3, the FastCGI transport's splitPos() in modules/caddyhttp/reverseproxy/fastcgi/fastcgi.go misuses golang.org/x/text/search with search.IgnoreCase when the request path contains a non-ASCII byte. Two distinct flaws in that fallback let an attacker mislead Caddy's FastCGI splitting into treating a non-.php (or other configured split_path extension) file as a script. In any deployment where the attacker can place content into a file served via FastCGI (uploads, file storage, etc.), this can be escalated to remote code execution by crafting a URL whose path triggers either flaw. This vulnerability is fixed in 2.11.3.
Quoted from the CVE Program record.