Security readout for executives and security teams
Plain-English summary
CVE-2026-27587 affects Caddy before 2.11.1. A routing rule using percent-escaped path patterns can be bypassed by changing letter casing in the request path. If access control depends on those routes, unauthorized users may reach protected content or handlers. The vendor fixed this in 2.11.1.
Executive priority
Prioritize remediation where Caddy gates access to sensitive applications or administrative paths. The issue is high severity but appears configuration-dependent, so risk is highest for deployments using escaped path matchers for access control.
Technical view
Caddy’s HTTP path matcher is intended to be case-insensitive. Before 2.11.1, match patterns containing %xx percent-escape sequences are compared against the escaped request path without lowercasing. This CWE-178 improper case handling can bypass path-based routing or controls tied to that route. CVSS 4.0 score is 7.7 high.
Likely exposure
Exposure is limited to Caddy deployments before 2.11.1 that use HTTP path matchers with percent-escape sequences and rely on those routes for routing or access controls.
Exploitation context
The CVE record describes network exploitation with low complexity, no privileges, and no user interaction. The provided sources do not report active exploitation, and the issue is not marked in KEV.
Researcher notes
Key review area is route/auth logic using Caddy HTTP path matchers with %xx patterns. Evidence provided names only Caddy before 2.11.1 as affected and 2.11.1 as fixed. No public exploit or KEV signal is included in the source bundle.
Mitigation direction
- Upgrade Caddy to version 2.11.1 or later.
- Review Caddy route rules using path matchers with percent-escaped patterns.
- Avoid relying solely on path routing for sensitive authorization decisions.
- Check the GitHub advisory and release notes for vendor guidance.
Validation and detection
- Inventory Caddy versions across internet-facing and internal services.
- Identify configurations using path matchers containing percent-escape sequences.
- Confirm protected routes are not dependent on vulnerable matcher behavior.
- Verify upgraded instances report Caddy 2.11.1 or later.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-178: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-27587 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.7 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
7.7HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/caddyserver/caddy/security/advisories/GHSA-g7pc-pc7g-h8jhCVE reference · x_refsource_CONFIRM
- https://github.com/caddyserver/caddy/releases/tag/v2.11.1CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Handling of Case Sensitivity
Improper Handling of Case Sensitivity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.