CVE-2026-59251
Denial of service via exponential certificate policy tree growth in path validation
Allocation of resources without limits in Erlang/OTP public_key certificate path validation allows a remote unauthenticated attacker to cause denial of service by sending a crafted X.509 certificate chain during the TLS handshake. During RFC 5280 policy processing in public_key:pkix_path_validation/3, the certificate policy tree maintained by pubkey_policy_tree grows without an upper bound. When a certificate chain contains M policies per certificate and K certificates, the tree grows on the order of M^K nodes because pubkey_policy_tree:add_leaves/2 and pubkey_policy_tree:add_leaf_siblings/2 extend the tree per policy per certificate. A modest chain with many policies per certificate is enough to pin BEAM schedulers and exhaust the node's memory, taking down the entire VM. The attacker only needs to be able to present a certificate chain to the victim, which is the normal precondition for a TLS handshake, so exploitation succeeds against any incoming or outgoing TLS connection that validates the peer's chain (the default for SSL/TLS clients and mutual-TLS servers). This is the same vulnerability class as OpenSSL's X509_verify_cert policy tree DoS. This vulnerability is associated with program files lib/public_key/src/pubkey_policy_tree.erl and program routines pubkey_policy_tree:add_leaves/2 and pubkey_policy_tree:add_leaf_siblings/2. This issue affects OTP from OTP 26.2 before OTP 27.3.4.15, OTP 28.5.0.4, and OTP 29.0.4, corresponding to public_key from 1.15 before 1.17.1.5, 1.20.3.4, and 1.21.4.
Fixes and workarounds
Fix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: EEFFix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: EEFAffected products and versions
| Product | Versions | Authority |
|---|---|---|
| OTP Erlang otp
software-id |
≥ 26.2; < * (affected, otp); unaffected at 27.3.4.15; unaffected at 28.5.0.4; unaffected at 29.0.4
Other versions: unaffected |
CNA: EEF |
| OTP Erlang public_key
otp |
≥ 1.15; < * (affected, otp); unaffected at 1.17.1.5; unaffected at 1.20.3.4; unaffected at 1.21.4
Other versions: unaffected |
CNA: EEF |
| OTP Erlang erlang/otp
github |
≥ 9d1dda7bad5a64b58c10a1554751689e94131a73; < * (affected, git); unaffected at f8580fc117098c08165f46c26fd0750c5cfb2a90; unaffected at f04c6bba38de1cf1b1836a7d9a9fbe239bd939e8
Other versions: unaffected |
CNA: EEF |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 4.0 / 8.7 high |
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L | CNA: EEF |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://github.com/erlang/otp/security/advisories/GHSA-622p-qfh6-c352CNA: EEF · vendor-advisory, related
- https://cna.erlef.org/cves/CVE-2026-59251.htmlCNA: EEF · related
- https://osv.dev/vulnerability/EEF-CVE-2026-59251CNA: EEF · related
- https://www.erlang.org/doc/system/versions.html#order-of-versionsCNA: EEF · x_version-scheme
- https://github.com/erlang/otp/commit/9d1dda7bad5a64b58c10a1554751689e94131a73CNA: EEF · related
- https://github.com/erlang/otp/commit/f8580fc117098c08165f46c26fd0750c5cfb2a90CNA: EEF · patch
- https://github.com/erlang/otp/commit/f04c6bba38de1cf1b1836a7d9a9fbe239bd939e8CNA: EEF · patch
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.