CVE-2026-93578: Netty OCSP Client Auth Bypass Vulnerability

CVE-2026-93578 Overview

CVE-2026-93578 is a certificate validation flaw in Netty's Online Certificate Status Protocol (OCSP) Client. The client fails to verify the id-kp-OCSPSigning Extended Key Usage (EKU) in OCSP responder certificates. An attacker holding any valid certificate from the same Certificate Authority (CA) can forge GOOD OCSP responses for revoked certificates. Applications relying on Netty's OCSP Client then accept certificates that should have been rejected, resulting in an authorization bypass. The weakness is categorized under [CWE-1035] and affects certificate revocation trust decisions in TLS-dependent Netty applications.

Critical Impact
Attackers can bypass certificate revocation checks and impersonate revoked identities to Netty-based clients, undermining TLS trust.

Affected Products

Netty OCSP Client component (all versions prior to the fixed release)
Applications embedding Netty for TLS termination or client-side certificate validation
Downstream distributions tracked in the Red Hat CVE-2026-93578 Advisory

Discovery Timeline

2026-09-18 - CVE-2026-93578 published to NVD
2026-09-18 - Last updated in NVD database

Technical Details for CVE-2026-93578

Vulnerability Analysis

The flaw resides in how Netty's OCSP Client validates responder certificates. RFC 6960 requires OCSP responses to be signed either by the issuing CA directly or by a delegated responder whose certificate carries the id-kp-OCSPSigning Extended Key Usage. Netty's client omits the EKU check, treating any certificate chained to the trusted CA as a valid OCSP signer. This turns revocation status validation into a trust decision based only on CA chaining. An attacker who legitimately obtained any certificate from the same CA can therefore sign OCSP responses. The consequence is a silent authorization bypass: revoked TLS certificates continue to be accepted by Netty consumers.

Root Cause

The root cause is a missing EKU enforcement step during OCSP response signature verification. The client trusts the signer based on issuer chaining alone, without asserting that the signer was delegated OCSP responsibility by the CA.

Attack Vector

Exploitation is network-based and requires no privileges or user interaction, but attack complexity is high. The attacker must possess a valid leaf certificate from the same CA as the target and be able to intercept or respond to OCSP queries. With those conditions met, the attacker forges a GOOD OCSP response for a revoked certificate, signs it with their leaf certificate, and delivers it to the Netty client. See the Red Hat Bug Report #2536969 for additional technical context.

// No verified proof-of-concept code is published for CVE-2026-93578.
// Refer to the Red Hat advisory for technical details.

Detection Methods for CVE-2026-93578

Indicators of Compromise

OCSP responses signed by end-entity certificates that lack the id-kp-OCSPSigning EKU.
TLS sessions completing successfully against endpoints whose certificates appear in published Certificate Revocation Lists (CRLs).
Unexpected OCSP responder identities appearing in TLS handshake telemetry for internal services.

Detection Strategies

Inspect OCSP response signer certificates at network egress and alert when the id-kp-OCSPSigning EKU is absent.
Correlate revocation feeds (CRLs, CT logs) with observed TLS connections to identify accepted revoked certificates.
Perform software composition analysis (SCA) across Java services to enumerate Netty versions running vulnerable OCSP client code.

Monitoring Recommendations

Ingest TLS and OCSP handshake metadata into a centralized analytics pipeline for revocation-status correlation.
Track outbound OCSP traffic patterns and alert on responder identities that deviate from CA-published delegations.
Monitor CA issuance events for unusual leaf certificates that could be repurposed to sign OCSP responses.

How to Mitigate CVE-2026-93578

Immediate Actions Required

Inventory all Java applications embedding Netty and identify services that enable OCSP validation.
Upgrade Netty to the fixed release referenced in the Red Hat CVE-2026-93578 Advisory as soon as it is available for your distribution.
Rotate and revoke any CA-issued certificates suspected of misuse for OCSP signing.

Patch Information

Red Hat is tracking remediation through the advisory and Red Hat Bug Report #2536969. Consumers should apply upstream Netty updates that enforce the id-kp-OCSPSigning EKU on OCSP responder certificates and rebuild dependent applications once fixed artifacts are released.

Workarounds

Enable CRL-based revocation checking in addition to OCSP so revoked certificates are rejected even if OCSP validation is bypassed.
Pin OCSP responder certificates for critical services to prevent acceptance of arbitrary CA-issued signers.
Restrict trust anchors to CAs with strict issuance policies for OCSP responder delegation.

bash

# Configuration example: enforce CRL checking alongside OCSP in the JVM
-Dcom.sun.net.ssl.checkRevocation=true \
-Dcom.sun.security.enableCRLDP=true \
-Dcom.sun.security.ocsp.enable=true