How to Fix CVE-2026-32144: OTP (Bundle Sibling)

*By Sai Kiran Pandrala*

Last verified: 2026-05-25

CVE-2026-32144 is a sibling vulnerability in the same Erlang OTP advisory bundle as CVE-2026-28808. The same patched build closes every CVE in the bundle, so the remediation procedure for CVE-2026-32144 matches the primary write-up.

What is different about 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...

Impact is consistent with the bundle: a security bypass on the affected component. The patched build closes every code path in the advisory in one update.

How to fix CVE-2026-32144

Apply the patched build per the primary write-up: How to Fix CVE-2026-28808.

For a quick check, confirm the running version of OTP:

# Confirm the installed version via your package manager
dpkg -l | grep -i otp   # Debian/Ubuntu
rpm -qa | grep -i otp   # RHEL/CentOS/Rocky

Frequently asked questions

Is CVE-2026-32144 being actively exploited?

Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That status can change, so monitor the vendor advisory and the KEV catalog if the system is exposed.

How severe is CVE-2026-32144?

CVSS rates it 7.6 (High). Use that score to set your patch priority alongside the other items in your queue.

Do I have to take OTP offline to apply the patch?

It depends on the deployment. High-availability or clustered installs can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.

What if my vulnerability scanner still flags CVE-2026-32144 after I patch?

Re-run the scan after a service restart, then confirm the scanner's plugin set is up to date. Some scanners detect by banner version only and lag the official fix metadata by a release.

References

• Official vendor advisory: https://github.com/erlang/otp/security/advisories/GHSA-gxrm-pf64-99xm
• NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-32144
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
• Primary write-up: How to Fix CVE-2026-28808

*Written by Sai Kiran Pandrala. Last verified 2026-05-25. Part of the Erlang OTP advisory bundle. Full procedure at how-to-fix-cve-2026-28808.*