caddyserver · Caddy · published 2026-06-23
CVE-2026-52846Caddy: stripHTML template function bypass
This month Public proof-of-concept exists (SSVC exploitation: poc).
CVE-2026-52846 has a public proof-of-concept exploit, but no confirmed exploitation in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 16% of all CVEs. This Caddy vulnerability: CVSS 4.2 (v3.1). Fixed upstream in Caddy 2.11.4. Patch in your normal monthly cycle.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Caddy 2.11.4.
Patch events
Web serverCaddy
Caddy security release: 2.11.4
Upgrade to
2.11.4Why: CVE-2026-52845: 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.2% (16th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 4.2 (v3.1)CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N | CNA / CISA ADP |
| SSVC exploitation | poc | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- caddyserver caddy
< 2.11.4(affected)
Description (from the CVE record)#
Caddy is an extensible server platform that uses TLS by default. Prior to 2.11.4, Caddy’s stripHTML template function cannot reliably remove all HTML tags from input strings. Certain malformed HTML, such as <<>img src=x onerror=alert()>, can bypass the tag-stripping logic, potentially leaving dangerous content in the output if it is later rendered as HTML. This may allow client-side XSS in cases where untrusted strings are rendered unsafely. This vulnerability is fixed in 2.11.4.
Quoted from the CVE Program record.