Caddy 2.11.9 upgrade: FastCGI security fixes, 3 breaking changes

released
lab run
upgraded from
2.11.8
guest
Debian 13 container
tested
yes, in our lab

Summary

Caddy 2.11.9 is a quick follow-up to 2.11.8. It fixes a regression in 2.11.8 and several security issues, mostly in FastCGI. The maintainers say that if you are on 2.11.8 and serve PHP, you should upgrade.

Reported in the release notes:

  • PHP directory indexes such as /wp-admin/ stopped reaching index.php in 2.11.8 and usually returned 404. This is fixed (#8352).
  • Path matchers with placeholders like {env.FOO} are no longer lower-cased before lookup (#8343).
  • New plain_time_format option for file_server browse (#8084).
  • Fewer allocations in path cleaning, header rewriting and weighted_round_robin.
  • go-jose updated to v4.1.6.

Breaking changes and deprecations

All of these are reported in the release notes. The notes also warn that the security patches may break apps that relied on the buggy behaviour.

  • Two site blocks that share TLS connection policies for the same hostname but set different client_auth are now a Caddyfile error. Before, the first one was kept and the other silently dropped (#8306).
  • FastCGI returns 400 when the escaped path and the decoded path would select different scripts, for example /public/tool.php%2f..%2f..%2fadmin%2ftool.php (#8357).
  • On Windows, FastCGI returns 400 for script paths with an 8.3 short name or a : (#8356).
  • FastCGI env values now win over request headers. If your app relied on clients overriding HTTP_* variables, that stops working (#8358).

Security fixes reported: GHSA-q34h-28rj-5hjm (clients overriding HTTP_* variables set by env), GHSA-9cr8-wmhh-39pm (Windows 8.3 names and alternate data streams), a mismatch between matcher and executed script, an HTTP/2 host vs :authority mismatch (#8355), and GHSA-mgcc-cww5-fp2q in go-jose.

Tested in our lab

We upgraded a plain Caddy install from 2.11.8 to 2.11.9 on a Debian 13 container, using the official release binaries and a systemd service.

  • The service stopped cleanly, started on 2.11.9, and was active afterwards.
  • A static site served the same pages before and after: /, /app/ and /app.
  • The same Caddyfile validated on 2.11.9, and the journal had no error-level log lines.

What we did not test: PHP/FastCGI, Windows, and the HTTP/2 host fix. The 2.11.8 directory-index regression did not show up in our simple try_files {path} {path}/index.html setup with static files, so we can’t confirm that fix either. We also tried a Caddyfile with two sites with different client_auth settings; both versions accepted it, so our config did not trigger the new error (the sites probably did not share a policy). Don’t read this as a test of that change.

Lab log

$ /opt/c/caddy version
v2.11.8 h1:E2pv1BoZ5bJaWqFkU6QvLa21iGAX8bDzlEQG4dDQ/Vc=
$ curl -si localhost:8080/app/ | sed -n "1p;\$p"
HTTP/1.1 200 OK
appindex
$ systemctl stop caddy
$ systemctl is-active caddy
inactive
[...]
$ systemctl start caddy
$ /opt/c/caddy version
v2.11.9 h1:bhZtcRKQOq0fuLvEgCdPYvUxXyGn9kzjG4lh2332DTE=
$ systemctl is-active caddy
active
$ curl -si localhost:8080/app/ | sed -n "1p;\$p"
HTTP/1.1 200 OK
appindex
$ /opt/c/caddy validate --config /etc/caddy.conf --adapter caddyfile
Valid configuration

Reported by others

Nothing beyond the release notes was checked. Source: Caddy v2.11.9 release notes.

Verdict

Upgrade now if you run PHP or any FastCGI backend, especially if you use env to pass identity values like HTTP_X_AUTH_USER. Before upgrading, check for sites with different client_auth settings on the same hostname, and for apps that depended on header-overridable FastCGI variables. For plain static or reverse-proxy setups, the upgrade was uneventful in our lab.

sources

other Caddy releases