Erlang · Erlang/OTP · published 2026-04-07

CVE-2026-32144OCSP designated-responder authorization bypass via missing signature verification

Routine No exploitation evidence; EPSS 0.2%.

CVE-2026-32144 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 11% of all CVEs. This Erlang/OTP vulnerability: CVSS 7.6 (v4.0), a successful attack gives total control of the component. Fixed upstream in Erlang/OTP 28.4.2, 27.3.4.10, 26.2.5.19. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Erlang/OTP 28.4.2, 27.3.4.10, 26.2.5.19.

Patch events

  1. This monthSecurity release

    Language runtimeErlang/OTP

    Erlang/OTP security releases: 28.4.2, 27.3.4.10, 26.2.5.19

    Upgrade to 28.4.227.3.4.1026.2.5.19

    Why: Vendor security release for server software (most severe: CVE-2026-28808).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.2% (12th pct)FIRST EPSS v2026.06.15
CVSS base score7.6 (v4.0)
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:L/SI:L/SA:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impacttotalCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

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

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →