Go · Servers and applications
CVE-2026-45692
Remote Admin Authorization Bypass in "/config" API via Array Index Normalization in github.com/caddyserver/caddy
- Severity
- Low 3.8
- Published
- 19 May 2026
- Last changed
- 25 Oct 2026
- Added to UpHeron
- 22 Oct 2026
- Fixed in
- 2.11.3
- Exploit chance
- 0.2% in the next 30 daysHigher than 15% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · Needs an administrator account · No user action needed
- Attacker can
- Read some data · Change some data
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N- Also known as
- GHSA-x5w9-xh9r-mvfc, GO-2026-5743
- Sources
- NVD, OSV.dev and GitHub
Description
This report is not about a normal textual prefix-expansion case.
The issue here is that 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.
A remote admin client certificate restricted to the following path:
can still read and modify a different array element by requesting:
/config/apps/http/servers/srv/routes/01
This happens because:
- the authorization layer uses string prefix matching
- the /config traversal layer parses array indices numerically using strconv.Atoi()
So:
- authorization sees /.../01 as matching /.../0
- traversal resolves 01 to numeric index 1
- the request therefore targets routes[1], not routes[0]
This is not just a prefix-match quirk. It is an authorization-to-object mismatch.
This is a security bug in Caddy's own code:
Affected software
| Software | Affected versions |
|---|---|
CaddyServers and applications · cpe:a:caddyserver:caddy |
|
CaddyGo · osv:Go:github.com/caddyserver/caddy/v2 |
|
About Caddy
open source web server
- Share of websites with a known web server
- 1.3%W3Techs, Nov 2026
- Docker Hub pulls
- 770,668,265Docker Hub, 15 Nov 2026
- GitHub stars
- 79,049GitHub, 15 Nov 2026
- Forks
- 5,264GitHub, 15 Nov 2026
- Latest release
- v2.11.9GitHub, 15 Nov 2026
- Released
- 5 Nov 2026GitHub
- License
- Apache Software License 2.0Wikidata
- Written in
- GoWikidata
- First published on GitHub
- 13 Jan 2015GitHub
Website Source code Docker image
Vulnerabilities in Caddy
- In our list
- 30
- Published in the last 12 months
- 23
- Critical, last 12 months
- 0
- High, last 12 months
- 9
- Known exploited
- 1
- GHSA-f278-mgc7-46j3php_fastcgi authorization bypass via dot-segments in the request pathMedium 5.9 4 Nov 2026
- GHSA-jf74-f69g-hcj9file_server exposes private keys when the data directory falls back to ./caddyMedium 4 Nov 2026
- GHSA-69hv-5jfc-mvmvrewrite re-decodes {http.matchers.file.remainder}, bypassing path-based deny rulesMedium 4 Nov 2026
- GHSA-25cw-38mq-q7m6file matcher resolves /file/./ to a regular file, bypassing suffix path rulesMedium 4 Nov 2026
- GHSA-r766-rf9f-588hHost and :authority values with dot segments or slashes escape a {host}-based rootHigh 4 Nov 2026
- CVE-2026-55458Caddy has an RFC 7230 §6.1 compliance issue / Hop-by-hop headers that leak throughLow 2.9 13 Oct 2026
References
- NVD https://nvd.nist.gov/vuln/detail/CVE-2026-45692
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-45692
- GitHub Advisory Database https://github.com/advisories/GHSA-x5w9-xh9r-mvfc
- OSV.dev https://osv.dev/vulnerability/GO-2026-5743