OCSP designated-responder authorization bypass via missing signature verification

Open Source Vulnerabilities CVE-2026-32144

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 before OTP 28.4.2 and OTP 27.3.4.10, corresponding to public_key from 1.16 before 1.20.3 and 1.17.1.2, and ssl from 11.2 before 11.5.4 and 11.2.12.7.

Open Source Vulnerabilities EEF-CVE-2026-32144

## Summary 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 before OTP 28.4.2 and OTP 27.3.4.10, corresponding to public\_key from 1.16 before 1.20.3 and 1.17.1.2, and ssl from 11.2 before 11.5.4 and 11.2.12.7. ## Workaround For SSL users: \* Do not enable OCSP validation setting (current default is {stapling, no\_staple}) \* Use CRL-based revocation checking by setting the {crl\_check, true} SSL option instead For applications using public\_key:pkix\_ocsp\_validate/5 directly: \* Pass {is\_trusted\_responder\_fun, Fun} option with a function that validates trusted responder certificates \* Restrict OCSP responder access to trusted endpoints via network controls (only applicable if you control the OCSP infrastructure) ## Configuration SSL/TLS must be configured with OCSP stapling enabled (e.g., {stapling, staple}), or the application must call public\_key:pkix\_ocsp\_validate/5 directly. OCSP stapling is disabled by default ({stapling, no\_staple}).