CVE-2026-32144: Erlang OTP · Improper Certificate Validation
Affects Erlang OTPSource CVE Database V5
Not known to be exploited · CVSS 7.6 High : upgrade to 1.20.3 soon.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.20.3, 11.5.4, 28.4.2
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:L/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 7 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade OTP and public_key to 1.20.3; OTP and ssl to 11.5.4; OTP and erlang/otp to 28.4.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ErlangOTP | Affected
| Fixed in
|
| ErlangOTP | Affected
| Fixed in
|
| ErlangOTP | Affected
| Fixed in
|
Hexpublic_keypkg:hex/public_keyOther threats | Affected
| Fixed in– |
GitHubpublic_keypkg:github/public_keyOther threats | Affected
| Fixed in
|
GitHubsslpkg:github/sslOther threats | Affected
| Fixed in
|
CPE configurations (1)
cpe:2.3:a:erlang:erlang\/otp:*:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The Red Hat advisory linked does not explicitly state patch availability or mitigation steps. Until then, consider disabling OCSP stapling or using alternative certificate revocation checking methods if feasible in your environment.
Description
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.
References
- github.com/erlang/otp/security/advisories/GHSA-gxrm-pf64-99xm (opens in a new tab)
- cna.erlef.org/cves/CVE-2026-32144.html (opens in a new tab)
- osv.dev/vulnerability/EEF-CVE-2026-32144 (opens in a new tab)
- erlang.org/doc/system/versions.html (opens in a new tab)
- github.com/erlang/otp/commit/ac7ff528be857c5d35eb29c7f24106e3a16d4891 (opens in a new tab)
- github.com/erlang/otp/commit/49033a6d93a5be0ee0dce04e1fb8b4ae7de1e0c0 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-32144 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2455896 (opens in a new tab)
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-32144.json (opens in a new tab)