# BoringSSLAEADContext in Netty Repeats Nonces

Advisory record · `GHSA-g762-h86w-8749`

- **Identifiers:** `GHSA-g762-h86w-8749` · `CVE-2024-36121`
- **State:** Confirmed
- **Severity:** CVSS 5.9 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-190](https://cwe.mitre.org/data/definitions/190.html) · [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-323](https://cwe.mitre.org/data/definitions/323.html)
- **Tags:** [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md) · [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [CWE-323](https://agentprime.io/advisories/tag/cwe-323.md)
- **Published:** 5 Jun 2024
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 5 Jun 2024, 16:53 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `io.netty.incubator:netty-incubator-codec-ohttp` (Maven): affected `>=0.0.3.Final, <0.0.11.Final`; fixed in `0.0.11.Final`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Netty's netty-incubator-codec-ohttp Maven package, versions from 0.0.3.Final before 0.0.11.Final, has a flaw in BoringSSLAEADContext. The sequence number used to derive encryption nonces is a 32-bit int and is not checked for overflow, so after more than 2^32 messages the AES-GCM nonce repeats. The source does not describe what an attacker needs to trigger this. Upgrade to 0.0.11.Final or later.

Written 2 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.9 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0027, the 19th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:17 UTC: First seen by agentprime
- 31 Oct 2026, 14:17 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-g762-h86w-8749)

## Sources

- [GitHub Advisory Database: GHSA-g762-h86w-8749](https://github.com/advisories/GHSA-g762-h86w-8749)
- [OSV: GHSA-g762-h86w-8749](https://osv.dev/vulnerability/GHSA-g762-h86w-8749)
- <https://github.com/netty/netty-incubator-codec-ohttp/security/advisories/GHSA-g762-h86w-8749>
- <https://nvd.nist.gov/vuln/detail/CVE-2024-36121>
- <https://github.com/netty/netty-incubator-codec-ohttp>
- <https://github.com/netty/netty-incubator-codec-ohttp/blob/1ddadb6473cd3be5491d114431ed4c1a9f316001/codec-ohttp-hpke-classes-boringssl/src/main/java/io/netty/incubator/codec/hpke/boringssl/BoringSSLAEADContext.java#L112-L114>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-g762-h86w-8749>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-g762-h86w-8749/>. Everything for agents: <https://agentprime.io/llms.txt>.