Description
Caddy is an extensible server platform that uses TLS by default. From 2.4.0 until 2.11.3, the authorization layer and the /config traversal layer do not agree on what object the path refers to. In this case, a path authorized for one config object is accepted, but then resolves to a different config object during traversal. This happens because the authorization layer uses string prefix matching and the /config traversal layer parses array indices numerically using strconv.Atoi(). This vulnerability is fixed in 2.11.3.
Affected products
caddyserver: caddy
References2
- github.com/caddyserver/caddy/security/advisories/GHSA-x5w9-xh9r… ExploitVendor Advisory
- github.com/caddyserver/caddy/security/advisories/GHSA-x5w9-xh9r… ExploitVendor Advisory
Metrics
- CVSS 3.1
-
3.8
LOW
Score source: NVD
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N - EPSS — exploit probability
- 0% percentile: 15 · as of 16 November 2026
- CWE
- CWE-187CWE-863
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.