Erlang · Erlang/OTP · published 2026-05-27
CVE-2026-42789Non-CA certificate accepted as intermediate issuer in public_key path validation
Routine No exploitation evidence; EPSS 0.4%.
CVE-2026-42789 is not known to be exploited in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 33% of all CVEs. This Erlang/OTP vulnerability: CVSS 7.0 (v4.0). Fixed upstream in Erlang/OTP 29.1.2, 29.0.1, 28.5.0.8, 28.5.0.1 (+3 more). Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Erlang/OTP 29.1.2, 29.0.1, 28.5.0.8, 28.5.0.1, 27.3.4.19, 27.3.4.12, 26.2.5.21.
Patch events
Language runtimeErlang/OTP
Erlang/OTP security fixes: 3 CVEs
Upgrade to
29.1.229.0.128.5.0.828.5.0.127.3.4.1927.3.4.1226.2.5.21Why: Vendor security release for server software (most severe: CVE-2026-42790).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.4% (33th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 7.0 (v4.0)CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:H/SI:H/SA:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- Erlang OTP
17.0to before*(affected)
- Erlang OTP
0.22to before*(affected)
- Erlang OTP
84adefa331c4159d432d22840663c38f155cd4c1to before*(affected)0a05b7ca33fb0b3f0a6cb9ae34252bb3a74032b8to before*(unaffected)75ca4c0dc2bbdb286ac3c3fe89cb4b4d2b4dc333to before*(unaffected)82af606b5437c4de1276dbcc8855a47e88231226to before*(unaffected)
Description (from the CVE record)#
Improper Following of a Certificate's Chain of Trust vulnerability in Erlang OTP public_key (pubkey_cert module) allows a non-CA certificate to be accepted as an intermediate issuer, enabling certificate chain forgery. In lib/public_key/src/pubkey_cert.erl, pubkey_cert:validate_extensions/7 contains two flaws that together allow a certificate with basicConstraints cA:false and no keyUsage extension to be used as an intermediate issuer in a chain passed to public_key:pkix_path_validation/3: the cA:false clause recurses into the remaining extensions without rejecting the certificate when it is in issuer position, and the keyUsage check only fires when the extension is present, so a certificate lacking keyUsage entirely bypasses the keyCertSign enforcement. Any party holding an end-entity certificate with basicConstraints cA:false and no keyUsage extension, issued by any CA in the victim's trust store, can use that certificate's private key to sign forged leaf certificates for arbitrary identities. public_key:pkix_path_validation/3 accepts the resulting chain, and by extension every TLS or mTLS endpoint built on the OTP ssl application that relies on the default verifier is affected, including server identity verification on the client side and client certificate verification on mTLS servers. This issue affects OTP from OTP 17.0 before OTP 27.3.4.19, OTP 28.5.0.8, and OTP 29.1.2, corresponding to public_key from 0.22 before 1.17.1.7, 1.20.3.6, and 1.21.8. Whether OTP before OTP 17.0, corresponding to public_key before 0.22, is affected is unknown.
Quoted from the CVE Program record.