cve.bz

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

6.3 mediumEPSS 0.3%Fix available

Medium (6.3) in erlang erlang\/otp. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

6.3 medium
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

CVSS 3.1

3.7 low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 26th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-05-27. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-295 Improper Certificate Validation
CWE-672 Operation on a Resource after Expiration or Release
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
Assigned by
EEF (CNA)
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-42791 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-42791?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-42791?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-42791 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • erlang:erlang\/otp

Versions

From the CNA's record in the CVE List.

ProductAffected
Erlang OTP1.16 and later
Erlang OTP27.0 and later

Fixed in

ProductFixed in
Erlang OTP1.17.1.3
Erlang OTP1.20.3.1
Erlang OTP1.21.1
Erlang OTP27.3.4.12
Erlang OTP28.5.0.1
Erlang OTP29.0.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13erlang1:27.3.4.1+dfsg-1+deb13u3DEBIAN-CVE-2026-42791 DSA-6464-1
Debian14erlang1:27.3.4.12+dfsg-1DEBIAN-CVE-2026-42791
Ubuntu22.04:LTSerlang1:24.2.1+dfsg-1ubuntu0.8USN-8901-1
Ubuntu24.04:LTSerlang1:25.3.2.8+dfsg-1ubuntu4.8USN-8901-1
Ubuntu25.10erlangno fix listedUBUNTU-CVE-2026-42791
Ubuntu26.04:LTSerlang1:27.3.4.6+dfsg-1ubuntu0.2UBUNTU-CVE-2026-42791 USN-8901-1
UbuntuPro:14.04:LTSerlang1:16.b.3-dfsg-1ubuntu2.2+esm3USN-8901-1
UbuntuPro:16.04:LTSerlang1:18.3-dfsg-1ubuntu3.1+esm4USN-8901-1
UbuntuPro:18.04:LTSerlang1:20.2.2+dfsg-1ubuntu2+esm4USN-8901-1
UbuntuPro:20.04:LTSerlang1:22.2.7+dfsg-1ubuntu0.5+esm3USN-8901-1
Red Hathummingbird:1erlang27, erlang27-et, erlang27-wx and 36 more0:27.3.4.17-1.hum1RHSA-2026:63160
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0erlang27.1.3-160000.5.1SUSE-SU-2026:22082-1
openSUSELeap 16.0erlang27.1.3-160000.5.1openSUSE-SU-2026:20907-1
openSUSETumbleweederlang28.5.0.4-1.1openSUSE-SU-2026:11559-1
openSUSETumbleweederlang2727.1.3-2.1openSUSE-SU-2026:10947-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · SUSE · openSUSE.

Red Hat

Red Hat rates this Low.

Red Hat's statement

Red Hat rates this flaw as Low rather than Important because exploitation requires the attacker to possess the private key of an expired CA-designated OCSP responder certificate, and the affected OCSP stapling feature is not enabled by default in the Erlang ssl application. The direct impact is limited to integrity — a forged OCSP response is accepted, allowing a revoked certificate to appear valid.

Red Hat's mitigation

For TLS clients using the Erlang ssl application, disable OCSP stapling by setting {stapling, no_staple} in the client options, or switch to CRL-based revocation checking with {crl_check, true}.

For applications calling public_key:pkix_ocsp_validate/5 directly, validate the responder certificate's validity period in application code before calling the function.

ProductPackageStateAdvisory
Red Hat Hardened Imageserlang27-main-27.3.4.17-1.hum1Fixed 2026-09-03RHSA-2026:63160
Red Hat OpenStack Platform 16.2erlangNot affected
Red Hat OpenStack Platform 17.1erlangNot affected
Red Hat OpenStack Platform 18.0erlangNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-42791.

Attack patterns (CAPEC)

  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON