Skip to main content
VulnerabilityPublished Updated

CVE-2026-27586: caddyserver caddy · Improper Handling of Exceptional Conditions

Affects caddyserver caddySource CVE Database V5

0
Compare

Public exploit available · CVSS 8.8 High : upgrade to 2.11.1 as a priority.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 4.0 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.11.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade caddy and caddyserver/caddy to 2.11.1.

Affected software

ProductAffectedFixed in
caddyservercaddyAffected
  • <2.11.1
Fixed in
  • 2.11.1
GitHubcaddyserver/caddypkg:github/caddyserver/caddyOther threatsAffected
  • <2.11.1
Fixed in
  • 2.11.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should immediately upgrade caddyserver to version 2.11.1 or later, which contains the fix for this vulnerability. Until upgrading, administrators must verify the accessibility, correctness, and permissions of all private CA certificate files specified in trusted_ca_cert_file and trusted_ca_certs_pem_files to ensure they are present and readable by the server process. Implement monitoring and alerting for file changes, permission modifications, or errors related to these certificate files. Additionally, enable verbose logging for mTLS authentication processes to detect anomalies. Conduct regular audits of client certificate acceptance policies and verify that only intended CAs are trusted. Consider deploying network-level controls to restrict client access and using additional authentication factors where feasible. Finally, integrate this vulnerability check into continuous security assessments and configuration management to prevent recurrence.

Description

Caddy is an extensible server platform that uses TLS by default. Prior to version 2.11.1, two swallowed errors in `ClientAuthentication.provision()` cause mTLS client certificate authentication to silently fail open when a CA certificate file is missing, unreadable, or malformed. The server starts without error but accepts any client certificate signed by any system-trusted CA, completely bypassing the intended private CA trust boundary. Any deployment using `trusted_ca_cert_file` or `trusted_ca_certs_pem_files` for mTLS will silently degrade to accepting any system-trusted client certificate if the CA file becomes unavailable. This can happen due to a typo in the path, file rotation, corruption, or permission changes. The server gives no indication that mTLS is misconfigured. Version 2.11.1 fixes the vulnerability.

References

Community reviews

Loading reviews…