CVE-2026-42791
Medium 6.3No known exploitationFix availableOCSP responder certificate validity period not checked in public_key
Record last updated
CVSS score
Medium on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Higher than 26% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
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.
Weakness: CWE-295, CWE-672
Patching and mitigation
- Patch status
- Fix available (source: NVD (reference tagged Patch))
- Fix documented (source date)
- Mitigation
- * For TLS clients using the 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. Source (opens in a new tab)
- Vendor guidance
- github.com (opens in a new tab)
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Erlang | OTP | 1.16 | Not documented | CVE Program |
| Erlang | OTP | 27.0 | Not documented | CVE Program |
| Erlang | OTP | 2b1a742c651b90f8a7a1fb2ddde73f29915ea376 | Not documented | CVE Program |
| erlang | erlang/otp | from 27.0 before 27.3.4.12 | 27.3.4.12 | NIST NVD |
| erlang | erlang/otp | from 28.0 before 28.5.0.1 | 28.5.0.1 | NIST NVD |
| erlang | erlang/otp | from 29.0 before 29.0.1 | 29.0.1 | NIST NVD |
Timeline
Disclosure
CVE record published by EEF
Source: CVE Program (opens in a new tab)
Patch
Fix documented by NVD (reference tagged Patch)
Vendor guidance and references
- Fix commit 7995f1f in erlang/otp (opens in a new tab)patch
- Fix commit b3870e0 in erlang/otp (opens in a new tab)patch
- OCSP Responder Certificate Accepted After Expiry in public_key (opens in a new tab)mitigation, related, vendor advisory, vendor-advisory
- EEF CNA record for CVE-2026-42791 (opens in a new tab)related, third party advisory
- Introducing commit 2b1a742 in erlang/otp (opens in a new tab)related
- OSV record EEF-CVE-2026-42791 (opens in a new tab)related, third party advisory
- Erlang/OTP version ordering (opens in a new tab)product, x_version-scheme