Skip to content
major vulnerability· requires attention

Widely used Netty framework; memory leak can trigger pool exhaustion and outages across many services; patch available.

Infrastructure

CVE-2026-48006

8.7
High
EPSS 0.74%Patch availableJun 13, 2026

Netty RedisArrayAggregator leaks direct buffers, exhausting memory.

common questions

Is CVE-2026-48006 being exploited?

Not confirmed. CVE-2026-48006 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.74% probability of exploitation in the next 30 days.

How severe is CVE-2026-48006?

CVE-2026-48006 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-48006?

Yes. A fix has been recorded for CVE-2026-48006. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-48006 affect?

CVE-2026-48006 affects Netty 4.1.x before 4.1.135.Final, Netty 4.2.x before 4.2.15.Final, Apps using Netty RedisArrayAggregator. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-48006?

Upgrade to patched Netty versions (4.1.135.Final/4.2.15.Final)

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Netty 4.1.x before 4.1.135.FinalNetty 4.2.x before 4.2.15.FinalApps using Netty RedisArrayAggregator
impact

Direct-memory pool exhaustion from leaked buffers can cause Netty channel/connection failures and outages.

action required

Patch when possible

affected versions
netty netty
  • affected>= 4.2.0.Final and < 4.2.15.Final
  • affected< 4.1.135.Final

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free