How severe is CVE-2025-24970?

CVE-2025-24970 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2025-24970?

CVE-2025-24970 affects the following packages: io.netty:netty-handler (Maven). Ecosystems affected: Maven.

How do I fix CVE-2025-24970?

Update io.netty:netty-handler to 4.1.118.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-24970 is resolved across your whole dependency graph.

How do I detect CVE-2025-24970 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.netty:netty-handler, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-24970 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2025-24970 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-24970 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-24970?

CVE-2025-24970 has an EPSS (Exploit Prediction Scoring System) score of 2.2%, placing it in the 83th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-24970?

CVE-2025-24970 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-24970 published, and has it been updated?

CVE-2025-24970 was published on February 10, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2025-24970 — netty-handler

HIGHFix: netty/netty@87f4072

CVE-2025-24970 is a high-severity (CVSS 7.5) Improper Input Validation vulnerability in io.netty:netty-handler. A fix is available for io.netty:netty-handler — see the affected versions and patch details below.

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

Also known asGHSA-4g8c-wm8x-jfhw

Published

Feb 10, 2025

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-24970.

EPSS Exploitation Probability

via FIRST.org ↗

2.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs83th percentile — riskier than 83% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕io.netty:netty-handler

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

When a special crafted packet is received via SslHandler it doesn't correctly handle validation of such a packet in all cases which can lead to a native crash.

Workarounds

As workaround its possible to either disable the usage of the native SSLEngine or changing the code from:

SslContext context = ...;
SslHandler handler = context.newHandler(....);

to:

SslContext context = ...;
SSLEngine engine = context.newEngine(....);
SslHandler handler = new SslHandler(engine, ....);

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.netty:netty-handler`	≥ 4.1.91.Final&&< 4.1.118.Final	4.1.118.Final`io.netty:netty-handler:4.1.118.Final`

Affected Products

3 products · 5 configurations

Application

active iq unified managernetapp

all

Application

oncommand insightnetapp

all

Application

nettynetty

≥ 4.1.91 && < 4.1.118

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.netty:netty-handler, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.netty:netty-handler to 4.1.118.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-24970 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This vulnerability in Netty's SslHandler is of important severity rather than moderate because it directly impacts the stability and reliability of applications using native SSLEngine. By sending a specially crafted packet, an attacker can trigger a native crash, leading to a complete process termination. Unlike…

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for CVE-2025-24970 (CC BY 4.0)

Product	Fixed in	Advisory
HawtIO HawtIO 4.2.0	`netty-handler`	RHSA-2025:8761
Red Hat build of Apache Camel 4.8.5 for Spring Boot	`netty-handler`	RHSA-2025:3543
Red Hat Build of Apache Camel 4.8 for Quarkus 3.15	`netty-handler`	RHSA-2025:2067
Red Hat build of Quarkus 3.15.3.SP1	`netty-handler`	RHSA-2025:1885
Red Hat build of Quarkus 3.20.1.redhat	`io.netty/netty-handler:4.1.119.Final-redhat-00005`	RHSA-2025:8258
Red Hat build of Quarkus 3.8.6.SP3	`netty-handler`	RHSA-2025:1884
Red Hat Data Grid	`netty-handler`	RHSA-2025:2663
Red Hat JBoss Enterprise Application Platform	`io.netty/netty-handler:4.1.124.Final-redhat-00001`	RHSA-2025:3467

Frequently Asked Questions

### Impact When a special crafted packet is received via SslHandler it doesn't correctly handle validation of such a packet in all cases which can lead to a native crash. ### Workarounds As workaround its possible to either disable the usage of the native SSLEngine or changing the code from: ``` SslContext context = ...; SslHandler handler = context.newHandler(....); ``` to: ``` SslContext context = ...; SSLEngine engine = context.newEngine(....); SslHandler handler = new SslHandler(engine, ....); ```