Erlang · Erlang/OTP · published 2026-05-27

CVE-2026-42791OCSP responder certificate validity period not checked in public_key

Routine No exploitation evidence; EPSS 0.3%.

CVE-2026-42791 is not known to be exploited in the wild. EPSS estimates a 0.3% chance of exploitation in the next 30 days, higher than 26% of all CVEs. This Erlang/OTP vulnerability: CVSS 6.3 (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.

Share this

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

  1. This monthSecurity release

    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.21

    Why: Vendor security release for server software (most severe: CVE-2026-42790).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.3% (26th pct)FIRST EPSS v2026.06.15
CVSS base score6.3 (v4.0)
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

Improper Certificate Validation vulnerability in Erlang OTP public_key (pubkey_ocsp module) allows forged OCSP responses signed with an expired responder certificate to be accepted as valid. OCSP response verification in pubkey_ocsp:verify_response/5 and pubkey_ocsp:is_authorized_responder/3 in lib/public_key/src/pubkey_ocsp.erl does not check the validity period (notBefore/notAfter) of the OCSP responder certificate. An attacker who has obtained the private key of an expired CA-designated OCSP responder certificate can forge OCSP responses that Erlang/OTP accepts as valid. This affects TLS clients using OCSP stapling via the ssl application: a malicious or compromised server can present a revoked TLS certificate together with a forged OCSP response signed by an expired responder key, and the client will accept the revoked certificate as valid. It also affects applications calling public_key:pkix_ocsp_validate/5 directly, where the impact depends on the use case — server-side client certificate validation using this API may allow authentication bypass with a revoked client certificate. This issue affects OTP from OTP 27.0 before OTP 27.3.4.12, OTP 28.5.0.1, and OTP 29.0.1, corresponding to public_key from 1.16 before 1.17.1.3, 1.20.3.1, and 1.21.1.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →