OCSP authorization bypass via missing signature verification
Published Apr 7, 2026 · Updated Apr 7, 2026
Improper certificate validation in affected Erlang/OTP releases allows man-in-the-middle attackers to make clients accept revoked certificates. The pubkey_ocsp:is_authorized_responder/3 routine trusts a designated responder when issuer names and OCSPSigning usage match, without verifying its certificate signature against the issuing CA. Exploitation requires OCSP stapling, which is disabled by default, or direct use of pkix_ocsp_validate/5; a forged response bypasses revocation checks and can expose data sent to a compromised server.
Summary
What happened
Improper certificate validation in affected Erlang/OTP releases allows man-in-the-middle attackers to make clients accept revoked certificates. The pubkey_ocsp:is_authorized_responder/3 routine trusts a designated responder when issuer names and OCSPSigning usage match, without verifying its certificate signature against the issuing CA. Exploitation requires OCSP stapling, which is disabled by default, or direct use of pkix_ocsp_validate/5; a forged response bypasses revocation checks and can expose data sent to a compromised server.
The record
- CVE
- CVE-2026-32144
- Published
- Apr 7, 2026
- Updated
- Apr 7, 2026
- Vendor
- Erlang
- Product
- Erlang/OTP
- Classifications
- CWE-295, CAPEC-459, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 7, 2026CVE publishedPublication date reported by the CVE source.
- Apr 7, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=11.2 <* changes=[{"at":"11.5.4","status":"unaffected"},{"at":"11.2.12.7","status":"unaffected"}]
- Affected versionversion=1.16 <* changes=[{"at":"1.20.3","status":"unaffected"},{"at":"1.17.1.2","status":"unaffected"}]
- Affected versionversion=27.0 <* changes=[{"at":"28.4.2","status":"unaffected"},{"at":"27.3.4.10","status":"unaffected"}]
- Affected versionversion=601a012837ea0a5c8095bf24223132824177124d <* changes=[{"at":"ac7ff528be857c5d35eb29c7f24106e3a16d4891","status":"unaffected"},{"at":"49033a6d93a5be0ee0dce04e1fb8b4ae7de1e0c0","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo