LiveActive security incident?Get immediate response
CVE Record

CVE-2026-27590: Caddy: Unicode case-folding length expansion causes incorrect split_path index (SCRIPT_NAME/PATH_INFO confusion) in FastCGI transport

Caddy is an extensible server platform that uses TLS by default. Prior to version 2.11.1, Caddy's FastCGI path splitting logic computes the split index on a lowercased copy of the request path and then uses that byte index to slice the original path. This is unsafe for Unicode because `strings.ToLower()` can change UTF-8 byte length for some characters. As a result, Caddy can derive an incorrect `SCRIPT_NAME`/`SCRIPT_FILENAME` and `PATH_INFO`, potentially causing a request that contains `.php` to execute a different on-disk file than intended (path confusion). In setups where an attacker can control file contents (e.g., upload features), this can lead to unintended PHP execution of non-.php files (potential RCE depending on deployment). Version 2.11.1 fixes the issue.

HighCVSS 8.9Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-27590 affects Caddy before 2.11.1 when handling FastCGI path splitting for PHP-style requests. A Unicode lowercasing bug can make Caddy split paths incorrectly, potentially causing the wrong file to be treated as executable PHP. Risk is highest where users can upload or influence files on the web server.

Executive priority

High priority for organizations running Caddy with PHP/FastCGI, especially public sites with uploads. Patch promptly because the issue may allow unintended PHP execution. Lower priority only where Caddy is not used, not internet-facing, or not configured with relevant FastCGI path handling.

Technical view

Caddy computed a split index on a lowercased request path, then applied that byte index to the original UTF-8 path. Some Unicode case-folding changes byte length, creating SCRIPT_NAME, SCRIPT_FILENAME, and PATH_INFO confusion. In affected FastCGI setups, a request containing .php may execute a different on-disk file than intended. Fixed in Caddy 2.11.1.

Likely exposure

Internet-facing Caddy deployments before 2.11.1 using FastCGI path splitting, especially for PHP, are the primary concern. Exposure increases if the application permits uploads or attacker-controlled file content. The provided sources identify Caddy as affected; do not assume unrelated products are vulnerable without vendor confirmation.

Exploitation context

The bundle does not show CISA KEV listing or confirmed active exploitation. The CVSS vector marks exploit maturity as proof-of-concept, and the described impact can reach remote code execution depending on deployment. Treat as urgent for PHP/FastCGI sites with upload functionality.

Researcher notes

Evidence is sufficient for affected version and fix: Caddy before 2.11.1, fixed in 2.11.1. The supplied description links impact to Unicode case-folding length expansion and FastCGI variable confusion. Active exploitation is not established in the provided sources.

Mitigation direction

  • Upgrade Caddy to version 2.11.1 or later.
  • Prioritize internet-facing FastCGI/PHP deployments.
  • Review Caddy and related vendor advisories for deployment-specific guidance.
  • Reduce or isolate attacker-controlled file upload paths where feasible.

Validation and detection

  • Inventory Caddy versions and flag anything before 2.11.1.
  • Identify sites using Caddy FastCGI path splitting for PHP.
  • Check whether users can upload or modify served files.
  • Confirm upgraded hosts report Caddy 2.11.1 or later.
  • Review logs for unusual Unicode paths containing .php.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-180: 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 lookup
cwe · low confidence lookup

CWE-20: 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 lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-27590 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.9 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
8.9CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

8.9High
CVSS 4.0 vector shape for CVE-2026-27590Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
caddyservercaddy< 2.11.1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-180 · source CWE mapping

Incorrect Behavior Order: Validate Before Canonicalize

Incorrect Behavior Order: Validate Before Canonicalize represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-20 · source CWE mapping

Improper Input Validation

Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.