CVE-2026-45389: OCaml-TLS Client Certificate Validation Bypass (CVSS 7.4)

Technical summary

CVE-2026-45389 is a certificate validation bypass in OCaml-TLS versions prior to 2.1.0. During mutual TLS (mTLS) authentication, the server accepts client certificates without sufficiently checking whether those certificates are actually marked for client authentication purposes. The KeyUsage and ExtendedKeyUsage X.509 extensions—critical fields that restrict certificate usage to specific purposes—are not properly enforced. This allows an attacker to reuse a general-purpose or server certificate (or similar misconfigured certificate) for client authentication, circumventing the intended access controls. The vulnerability maps to CWE-295 (Improper Certificate Validation).

Business impact

Systems using OCaml-TLS for client certificate authentication lose a critical trust boundary. An attacker holding any certificate signed by the same Certificate Authority can impersonate legitimate clients, potentially gaining unauthorized access to protected resources. In microservices architectures, cloud environments, or enterprises using certificate-based access control (zero-trust, mTLS), this creates a significant lateral movement vector. Confidentiality and integrity of client-server communications can be compromised, though availability is not directly affected.

Affected systems

OCaml-TLS library versions before 2.1.0 are vulnerable. This includes any application or service built on OCaml-TLS that performs client certificate authentication. Verify your dependency tree and supply chain; OCaml-TLS may be used as an indirect dependency in larger OCaml-based projects, containerized services, or embedded cryptographic stacks.

Exploitability

Exploitation requires the attacker to possess a certificate valid for the target Certificate Authority—a non-trivial precondition, but realistic in scenarios where CA compromise has occurred or where internal enterprise CAs issue broadly-purposed certificates. The attack is network-accessible and requires no user interaction or special privileges. Network complexity is rated as high, likely reflecting the need to intercept or initiate connections at the right endpoint. Overall CVSS 7.4 (HIGH) reflects meaningful but not maximum impact.

Remediation

Upgrade OCaml-TLS to version 2.1.0 or later. This release includes corrected certificate validation logic that enforces KeyUsage and ExtendedKeyUsage checks. After patching, conduct certificate audits to ensure all issued certificates contain appropriate extension constraints for their intended use cases.

Patch guidance

Update the OCaml-TLS dependency to version 2.1.0 as confirmed in the official vendor advisory. This is a security update and should be prioritized in your normal release cycle. Test the upgrade in a staging environment with client certificate authentication enabled to ensure no compatibility regressions. Rebuild and redeploy all affected services. No breaking changes are anticipated, but verify against OCaml-TLS release notes.

Detection guidance

Monitor TLS handshake logs and authentication events for any client certificates being accepted that lack proper KeyUsage or ExtendedKeyUsage markers. In mTLS deployments, audit the certificate chains presented by clients and cross-reference against your CA's issued certificate inventory. Look for unexpected certificate serial numbers or subjects connecting as clients. Network intrusion detection systems (IDS) may detect suspicious certificate chains if tuned to flag non-standard TLS parameters. Most reliably, enable detailed TLS session logging in your application and review for certificates that bypass expected validation gates.

Why prioritize this

This is a HIGH severity authentication bypass affecting certificate-based access control. Organizations heavily dependent on mTLS or client certificate authentication (particularly cloud-native, zero-trust, or federated identity systems) should prioritize this immediately. The attack requires Certificate Authority compromise or misissuance, which is a real risk in many enterprises. CVE-2026-45389 is not currently listed on CISA's Known Exploited Vulnerabilities (KEV) catalog, but the core flaw is straightforward enough that attack tools or POC code could emerge quickly once public scrutiny increases.

Risk score, explained

CVSS 3.1 score of 7.4 (HIGH) reflects: Attack Vector Network (AV:N)—remotely exploitable; Attack Complexity High (AC:H)—requires attacker to hold a valid certificate; Privileges Required None (PR:N)—no prior access needed; User Interaction None (UI:N)—no social engineering; Scope Unchanged (S:U)—no privilege escalation; Confidentiality High (C:H), Integrity High (I:H)—client identity spoofing enables unauthorized access and data tampering; Availability None (A:N)—no denial of service. The score appropriately captures a serious authentication weakness that enables impersonation but does not directly affect service availability.

Frequently asked questions