caddyserver/caddy
v2.11.9Curated backend / runtime repository (caddyserver/caddy) tracked via conditional GitHub .atom polling.
Caddy is an extensible, enterprise-ready web server with automatic HTTPS capabilities written in Go. It simplifies web infrastructure configuration through intuitive Caddyfiles and automated certificate management. This release addresses critical security advisories in FastCGI handling and fixes directory index routing regressions for PHP applications.
Patches critical FastCGI security vulnerabilities and routing regressions. Update immediately. Migration: Low.
Key Release Highlights (v2.11.9)
- Fixed PHP directory index resolution regressions introduced in
v2.11.8for trailing slash requests. - Patched multiple critical FastCGI security bypasses involving header spoofing, Windows 8.3 paths, and encoded dot segments.
- Enforced strict validation on conflicting
client_authdeclarations within TLS connection policies. - Updated
go-josedependency tov4.1.6addressingGHSA-mgcc-cww5-fp2q.
Breaking Changes (Action Required)
- Conflicting
client_authdefinitions across shared TLS connection policies now throw a Caddyfile error. - Ambiguous FastCGI script paths with mismatched escaped and decoded forms now trigger a
400response. - FastCGI
envconfiguration values now strictly take precedence over incoming client request headers.
go get github.com/caddyserver/caddy/v2@v2.11.9Ecosystem Compatibility Matrix & Verified Graph Warnings
Zero-Noise Historical Release Timeline (1)
Format: [Core Change] + [Required Action] + [Migration Effort]Patches critical FastCGI security vulnerabilities and routing regressions. Update immediately. Migration: Low.
Upgrade & Migration Q&A (caddyserver/caddy v2.11.9)
Direct Answers for Engineers & AI AgentsIs caddyserver/caddy v2.11.9 safe to upgrade in production?
caddyserver/caddy v2.11.9 is classified as SECURITY_PATCH (PATCH release). Patches critical FastCGI security vulnerabilities and routing regressions. Update immediately. Migration: Low.
What breaking changes or compatibility risks exist in caddyserver/caddy v2.11.9?
Conflicting client_auth definitions across shared TLS connection policies now throw a Caddyfile error. Ambiguous FastCGI script paths with mismatched escaped and decoded forms now trigger a 400 response. FastCGI env configuration values now strictly take precedence over incoming client request headers.
What is the bundle size impact of github.com/caddyserver/caddy/v2 v2.11.9?
Measured bundle size telemetry is currently unavailable for github.com/caddyserver/caddy/v2 v2.11.9; verify build output locally before deploying.
How do I upgrade github.com/caddyserver/caddy/v2 to v2.11.9?
Upgrade github.com/caddyserver/caddy/v2 to v2.11.9 by running "go get github.com/caddyserver/caddy/v2@v2.11.9" and applying the migration steps: go get github.com/caddyserver/caddy/v2@v2.11.9