dbcve.org
NettyApplication

CVE-2026-44250

HIGH · 7.5 CVSS v3.1 Published 2026-06-11
Fix available
A fix is available. Upgrade to 4.1.135 / 4.2.15 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Netty is a network application framework for development of protocol servers and clients. In netty-codec-redis prior to versions 4.1.135.Final and 4.2.15.Final, an attacker can cause DoS by sending a crafted Redis payload with deeply nested arrays. This forces the server to allocate a massive number of state objects and collections, leading to memory exhaustion and an OutOfMemoryError. Versions 4.1.135.Final and 4.2.15.Final patch the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The netty-codec-redis library prior to versions 4.1.135.Final and 4.2.15.Final contains a vulnerability where specially crafted Redis protocol messages with deeply nested arrays cause excessive memory allocation during parsing, leading to memory exhaustion and an OutOfMemoryError condition.

MitigationUpgrade netty-codec-redis to version 4.1.135.Final or 4.2.15.Final or later to patch the vulnerability; consider implementing connection limits and timeout controls as defense-in-depth.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
NettyApplication
Affected:< 4.1.135>= 4.2.0, < 4.2.15

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify netty-codec-redis as a dependency
    Review your project's dependency tree or build configuration (Maven pom.xml, Gradle build.gradle, or similar) to confirm the netty-codec-redis library is present.
    Affected if The netty-codec-redis library is included in your dependencies.
  2. Determine the installed netty-codec-redis version
    Locate the specific version of netty-codec-redis in your dependency management system, Maven repository, or bundled JAR file metadata.
    Affected if The version is less than 4.1.135.Final, or is 4.2.0 through 4.2.14.Final inclusive.
  3. Verify Redis protocol decoding is in use
    Inspect your application code and configuration to determine if Redis message parsing using netty-codec-redis is actively processing incoming data, such as through a Redis client or server implementation that uses the netty Redis codec.
    Affected if Your application deserializes or parses Redis protocol messages using the netty-codec-redis decoder.
  4. Confirm external input can reach the Redis parser
    Review your network exposure and channel pipeline configuration to determine if untrusted Redis protocol data from network sources can reach the netty-codec-redis decoder without prior validation.
    Affected if External or untrusted Redis protocol data can be passed directly to the netty-codec-redis decoder.

You are affected if your environment has netty-codec-redis version 4.1.x below 4.1.135 or 4.2.x below 4.2.15, and your application parses Redis protocol messages from potentially untrusted sources using the netty Redis codec.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.1.135 / 4.2.15 or later
Fixed in 4.1.1354.2.15
Interim mitigation

Upgrade netty-codec-redis to version 4.1.135.Final or 4.2.15.Final or later to patch the vulnerability; consider implementing connection limits and timeout controls as defense-in-depth.

Recommended fix High confidence

4.1.135.Final (for 4.1.x users) or 4.2.15.Final (for 4.2.x users)

  1. Identify the current Netty version in use by checking project dependencies (e.g., pom.xml, build.gradle, or Maven/Gradle artifacts)
  2. Determine which Netty 4.x branch is in use: 4.1.x or 4.2.x
  3. If using Netty 4.1.x (version < 4.1.135), upgrade to version 4.1.135.Final
  4. If using Netty 4.2.x (version >= 4.2.0 and < 4.2.15), upgrade to version 4.2.15.Final
  5. Update the dependency version in build configuration (pom.xml, build.gradle, or similar)
  6. Rebuild and redeploy the application
  7. Verify the application starts and functions correctly with the new version
Caveat Minimal risk - patch releases typically contain only bug fixes and security patches without API changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Netty Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44250 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44250 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data