Servers and applications
GHSA-6365-7ppr-5r92
Connection created for the wrong upstream for forward_auth + reverse_proxy
- Severity
- Medium
- Published
- 10 Jul 2026
- Last changed
- 10 Jul 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 2.11.5
- Sources
- Project advisories (GitHub)
Description
We have found an issue where Caddy is using the wrong connection when a handler has both forward_auth and reverse_proxy. Occasionally users were mentioning requests returning with 404 for not apparent reason. Unfortunately enabling detailed Caddy logs did not help as these were not correct, insisting their upstreams were returning 404 for endpoints which are known to exist. Only tcpdump showed the real issue; the request meant for the forward_auth endpoint was being sent on the wrong connection which did not have the expected endpoints and thus replied with 404.
For our setup we have downgraded to 2.10.2 which is not affected.
Commit 8aca108d2c9d9e9ff3a39ff00684ea58df1338f6 seems to be the cause as the parent 156ce99d3a46be8cefe8502b2c30b757e4deb79f does not exhibit this behavior.
This seems pretty severe, it randomly breaks the forward_auth behavior depending on timing. You could pass a foward_auth check unexpectedly if the raced connection happens to have the same endpoints and…
Affected software
| Software | Affected versions |
|---|---|
CaddyServers and applications · github:caddyserver/caddy |
|
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
- GitHub Advisory Database https://github.com/advisories/GHSA-6365-7ppr-5r92
- github.com https://github.com/caddyserver/caddy/security/advisories/GHSA-6365-7ppr-5r92