CVE-2026-56821
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NSummary
CVE-2026-56821 is a high-severity Improper Check for Certificate Revocation (CWE-299) vulnerability. Its CVSS base score is 7.4 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Adversary-in-the-Middle (T1557); ranked at the 4th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-2 (Flaw Remediation) and IA-5 (Authenticator Management) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-50090
Vulnerability Data
Netty is an asynchronous, event-driven network application framework. Prior to versions 4.1.136.Final and 4.2.16.Final, the OcspServerCertificateValidator flags an out-of-date OCSP response but does not stop processing it, so an expired GOOD response is still reported as VALID, letting an on-path…
more
attacker replay a stale GOOD response to bypass revocation of a since-revoked certificate. Exploitation can lead to certificate revocation bypass via replay of an expired OCSP response. Any application using OcspServerCertificateValidator is affected; a revoked certificate can be accepted. This issue has been fixed in versions 4.1.136.Final and 4.2.16.Final.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Vulnerability enables on-path MitM by allowing replay of stale OCSP GOOD responses to bypass certificate revocation checks.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly addresses the flaw by requiring application of the vendor patch (4.1.136.Final/4.2.16.Final) that enforces OCSP response freshness before accepting a GOOD status.
Requires management of authenticators including validation of certificate revocation status, which would reject the replayed stale OCSP response if properly implemented.
Mandates proper issuance, management and revocation handling for PKI certificates, preventing acceptance of certificates whose revocation status is not freshly verified.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Certificate-based authentication requires valid, non-revoked certificates; proper revocation checking is a core implementation detail of this control.
Protecting data-in-transit commonly relies on TLS certificate validation that includes revocation status checks.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Mandates use of cryptography including certificate validation and revocation checking.
Security testing can detect missing or incorrect certificate revocation checks.
Secure coding practices should include proper certificate revocation verification.
Requires secure authentication mechanisms that rely on valid certificates.
Network security controls can enforce certificate validation at network boundaries.
Security of network services includes certificate-based authentication and revocation checks.