# SslHandler doesn't correctly validate packets which can lead to native crash when using native SSLEngine

Advisory record · `GHSA-4g8c-wm8x-jfhw`

- **Identifiers:** `GHSA-4g8c-wm8x-jfhw` · `CVE-2025-24970`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-20](https://cwe.mitre.org/data/definitions/20.html)
- **Tags:** [CWE-20](https://agentprime.io/advisories/tag/cwe-20.md)
- **Published:** 10 Feb 2025
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 10 Feb 2025, 17:38 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `io.netty:netty-handler` (Maven): affected `>=4.1.91.Final, <4.1.118.Final`; fixed in `4.1.118.Final`

## Machine-written summary

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

> The io.netty:netty-handler package, versions from 4.1.91.Final before 4.1.118.Final, does not correctly validate a specially crafted packet received through SslHandler when the native SSLEngine is used. An attacker who can send such packets over the network can cause a native crash. Upgrade to 4.1.118.Final or later. The source also describes a workaround of disabling the native SSLEngine, but its code examples are omitted here.

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

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

- **CISA KEV:** Not listed.
- **EPSS:** 0.022, the 82nd percentile, on 14 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-4g8c-wm8x-jfhw)

## Sources

- [GitHub Advisory Database: GHSA-4g8c-wm8x-jfhw](https://github.com/advisories/GHSA-4g8c-wm8x-jfhw)
- [OSV: GHSA-4g8c-wm8x-jfhw](https://osv.dev/vulnerability/GHSA-4g8c-wm8x-jfhw)
- <https://github.com/netty/netty/security/advisories/GHSA-4g8c-wm8x-jfhw>
- <https://nvd.nist.gov/vuln/detail/CVE-2025-24970>
- <https://github.com/netty/netty/commit/87f40725155b2f89adfde68c7732f97c153676c4>
- <https://github.com/netty/netty>
- <https://security.netapp.com/advisory/ntap-20250221-0005>
- <https://www.vicarius.io/vsociety/posts/cve-2025-24970-netty-vulnerability-detection>
- <https://www.vicarius.io/vsociety/posts/cve-2025-24970-netty-vulnerability-mitigation>

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-4g8c-wm8x-jfhw>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-4g8c-wm8x-jfhw/>. Everything for agents: <https://agentprime.io/llms.txt>.