CVE-2026-27586: Caddy mTLS client authentication fails open on missing or malformed CA file

Overview

Caddy is an extensible server platform that uses TLS by default. CVE-2026-27586 describes a fail-open condition in its mTLS client certificate authentication. When the configured CA certificate file is missing, unreadable or malformed, the server still starts and accepts client certificates signed by any system-trusted CA.

Impact

• The private CA trust boundary that mTLS is meant to enforce can be bypassed.
• The server starts without error, so the misconfiguration is not visible at startup.
• The record rates the issue critical, with an NVD base score of 9.1 and a GitHub score of 8.8.

Affected products and versions

• Product: Caddy (Caddyserver Caddy).
• Affected: versions before 2.11.1.
• Fixed in: 2.11.1, according to the record description and the release notes. The record's structured fixes field is empty.

Exploitation status

• The record does not list this CVE in CISA KEV, so active exploitation is not claimed here.
• No confirmed exploitation in the wild appears in the sources consulted.
• SSVC lists exploitation as proof of concept and automatable as yes, which indicates that public proof-of-concept material may exist.
• The record includes a third-party reference tagged as exploit-related. Its content was not used in this analysis.

Remediation and mitigation

• Upgrade Caddy to 2.11.1 or a later release. The vendor advisory is the primary source for this issue.
• Until the upgrade is applied, confirm that every CA file referenced by mTLS directives exists, is readable and contains valid certificates.
• Validate Caddy configuration and file paths in deployment pipelines, and check them again after certificate rotation or permission changes.
• Restrict file permissions on CA bundles to the minimum required and monitor them for unexpected changes.
• Where possible, add network-level controls in front of mTLS-protected services as a compensating layer.

Detection guidance

• Inventory all deployments that use the trusted_ca_cert_file or trusted_ca_certs_pem_files options for mTLS.
• Do not rely on startup logs alone, because the record states the server gives no indication of the misconfiguration.
• In a controlled test environment, confirm that clients presenting certificates from CAs outside the intended trust chain are rejected.
• Monitor file integrity and access events for CA certificate files.

Limitations of the available information

• The record does not describe the exact code path beyond the two swallowed errors in ClientAuthentication.provision().
• The structured fixed-version list is empty, so the fixed version relies on the description and release reference.
• The CWE entry has no name in the record.
• The EPSS date in the record should be verified before use.
• No independent testing or real-world incident data was available for this analysis.

Frequently asked questions

Is CVE-2026-27586 known to be actively exploited?

The record does not list this CVE in CISA KEV, and no confirmed exploitation in the wild appears in the sources consulted. SSVC data indicates proof-of-concept status, which is a different level of evidence.

Which Caddy version fixes this issue?

According to the record, version 2.11.1 fixes the vulnerability. Affected versions are those before 2.11.1, so upgrading to 2.11.1 or a later release is the recommended remediation.

Why is this issue dangerous if the server starts normally?

Because the server does not report the misconfiguration, a missing or malformed CA file can silently allow client certificates from any system-trusted CA. Operators may not notice until the trust boundary has already been bypassed.

This analysis was drafted with AI assistance from verified source data and automatically checked against it.