PT-2026-30815 · Erlang · Otp
Jakub Witczak
·
Published
2026-04-07
·
Updated
2026-04-07
·
CVE-2026-32144
CVSS v4.0
7.6
High
| AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:L/SI:L/SA:N |
Improper Certificate Validation vulnerability in Erlang OTP public key (pubkey ocsp module) allows OCSP designated-responder authorization bypass via missing signature verification.
The OCSP response validation in public key:pkix ocsp validate/5 does not verify that a CA-designated responder certificate was cryptographically signed by the issuing CA. Instead, it only checks that the responder certificate's issuer name matches the CA's subject name and that the certificate has the OCSPSigning extended key usage. An attacker who can intercept or control OCSP responses can create a self-signed certificate with a matching issuer name and the OCSPSigning EKU, and use it to forge OCSP responses that mark revoked certificates as valid.
This affects SSL/TLS clients using OCSP stapling, which may accept connections to servers with revoked certificates, potentially transmitting sensitive data to compromised servers. Applications using the public key:pkix ocsp validate/5 API directly are also affected, with impact depending on usage context.
This vulnerability is associated with program files lib/public key/src/pubkey ocsp.erl and program routines pubkey ocsp:is authorized responder/3.
This issue affects OTP from OTP 27.0 until OTP 28.4.2 and 27.3.4.10 corresponding to public key from 1.16 until 1.20.3 and 1.17.1.2, and ssl from 11.2 until 11.5.4 and 11.2.12.7.
Fix
Improper Certificate Validation
Found an issue in the description? Have something to add? Feel free to write us 👾
Weakness Enumeration
Related Identifiers
Affected Products
Otp