CVE-2026-32144 remediation guide

Erlang OTP, Red Hat OpenStack Platform 16.2, Red Hat OpenStack Platform 17.1

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

Open CVE record

ProductErlang OTP, Red Hat OpenStack Platform 16.2, Red Hat OpenStack Platform 17.1

Affected versions>= 1.16, >= 11.2, >= 27.0, >= 601a012837ea0a5c8095bf24223132824177124d, >= 27.0 < 27.3.4.10, >= 28.0 < 28.4.2, >= 1.16 < 1.17.1.2, >= 1.18 < 1.20.3, >= 11.2 < 11.2.12.7, > 11.3 < 11.5.4

Fixed versions27.3.4.10, 28.4.2, 1.17.1.2, 1.20.3, 11.2.12.7, 11.5.4

Priority basisReview · CVSS 7.6 · EPSS 0.20%

Identify the affected asset

Confirm whether Erlang OTP, Red Hat OpenStack Platform 16.2, Red Hat OpenStack Platform 17.1 is installed, record the deployed version and installation path, and identify exposed interfaces.

Record the product name, package or appliance identifier, and installed version.
Identify internet-facing, administrative, API, and internal access paths.
Preserve the pre-change configuration and relevant service logs.

Validate the affected-version match

Compare the deployed version with the affected range: >= 1.16, >= 11.2, >= 27.0, >= 601a012837ea0a5c8095bf24223132824177124d, >= 27.0 < 27.3.4.10, >= 28.0 < 28.4.2, >= 1.16 < 1.17.1.2, >= 1.18 < 1.20.3, >= 11.2 < 11.2.12.7, > 11.3 < 11.5.4. Treat incomplete inventory results as unresolved.

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 27.3.4.10, 28.4.2, 1.17.1.2, 1.20.3, 11.2.12.7, 11.5.4. Preserve configuration and rollback material before change.

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

Confirm the expected version and package state.
Run a functional health check for critical service paths.
Review authentication, error, application, and security monitoring logs.
Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.