Skip to main content
CVE-2026-32144VulnerabilityPublished Updated

Erlang OTP public_key (pubkey_ocsp module) · Improper Certificate Validation Vulnerability

Affects erlangSource GCVE Database

0
Compare
Authoritative record:CVE-2026-32144· High 7.6

Not known to be exploited · CVSS 7.6 High : upgrade to 1:27.3.4.6+dfsg-1ubuntu0.2 soon.

Data as of 18 Nov 2026, 15:19 UTC

CVSS 4.0 base score
7.6High
How severe the flaw is on the 0–10 CVSS scale.

Sources agree

CVSS scores by source
CNA (EEF)CVSS 4.07.6
ADP (redhat-SADP)CVSS 3.17.4
Patch
Available – fixed in 1:27.3.4.6+dfsg-1ubuntu0.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 17 Nov 2026.

What to do

Upgrade the Ubuntu erlang package to 1:27.3.4.6+dfsg-1ubuntu0.2.

Affected software

ProductAffectedFixed in
Ubuntu 26.04 LTSerlangpkg:deb/ubuntu/erlang?arch=source&distro=resoluteOther threatsAffected
  • <1:27.3.4.6+dfsg-1ubuntu0.2
Fixed in
  • 1:27.3.4.6+dfsg-1ubuntu0.2
Ubuntu 25.10erlangpkg:deb/ubuntu/erlang?arch=source&distro=questingOther threatsAffected
  • 1:27.3.4.1+dfsg-1 – 1:27.3+dfsg-1ubuntu1.1
5 affected builds
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

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 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.

References

Community reviews

Loading reviews…