Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Medium severity, with a CVSS score of 4.3, published 19 May 2026.
- Which products and versions are affected?
- github.com/caddyserver/caddy/v2 (Go) < 2.11.3.
- Is there a fix for This vulnerability?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is This vulnerability attacked?
- It is attacked over the network, in a software library.
- Am I affected?
- Check whether you run github.com/caddyserver/caddy/v2 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An authorization bypass exists in Caddy's remote admin access control for PKI endpoints. The vulnerability stems from the use of `strings.HasPrefix` in `admin.go` to validate request paths against allowed permissions. Because the implementation does not enforce path-segment boundaries, a client certificate authorized for a specific path (e.g., `/pki/ca/prod`) can successfully access sibling resources (e.g., `/pki/ca/prod-backup`) that share the same prefix. This allows an authenticated attacker with limited administrative privileges to interact with unauthorized Certificate Authority (CA) resources. The issue is fixed in version 2.11.3 by implementing segment-aware path matching.
Affected products
- caddyserver caddy < 2.11.3
Timeline
- 2026-05-13: advisory: Initial GitHub Advisory published
- 2026-05-19: other: Advisory updated