NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

Netty's HttpPostRequestDecoder can OOMGHSA-5jpm-x58v-624v

MEDIUMFix: netty/netty@0d0c6ed

GHSA-5jpm-x58v-624v is a medium-severity (CVSS 5.3) CWE-770 vulnerability in io.netty:netty-codec-http. A fix is available for io.netty:netty-codec-http — see the affected versions and patch details below.

Also known asCVE-2024-29025
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 9, 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 GHSA-5jpm-x58v-624v.

EPSS Exploitation Probability

via FIRST.org ↗
1.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs72th percentile — riskier than 72% of all scored CVEsHighest risk
0.00%0.63%1.25%1.88%0.3%1.4%May 26Sep 26Nov 26

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-codec-http

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

Summary

The HttpPostRequestDecoder can be tricked to accumulate data. I have spotted currently two attack vectors

Details

  1. While the decoder can store items on the disk if configured so, there are no limits to the number of fields the form can have, an attacher can send a chunked post consisting of many small fields that will be accumulated in the bodyListHttpData list.
  2. The decoder cumulates bytes in the undecodedChunk buffer until it can decode a field, this field can cumulate data without limits

PoC

Here is a Netty branch that provides a fix + tests : https://github.com/vietj/netty/tree/post-request-decoder

Here is a reproducer with Vert.x (which uses this decoder) https://gist.github.com/vietj/f558b8ea81ec6505f1e9a6ca283c9ae3

Impact

Any Netty based HTTP server that uses the HttpPostRequestDecoder to decode a form.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenio.netty:netty-codec-httpall versions4.1.108.Finalio.netty:netty-codec-http:4.1.108.Final

Affected Products

2 products · 2 configurations
OS
debian linuxdebian
1 version
10.0
Application
nettynetty
< 4.1.108
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update io.netty:netty-codec-http to 4.1.108.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5jpm-x58v-624v is resolved across your whole dependency graph.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

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 HatModerate

The vulnerability in io.netty:netty-codec-http, allowing for Allocation of Resources Without Limits or Throttling issues, is assessed as moderate severity due to its potential impact on system availability and performance. By exploiting the flaw in HttpPostRequestDecoder, an attacker can craft chunked POST requests…

Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options don't 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 GHSA-5jpm-x58v-624v (CC BY 4.0)
ProductFixed inAdvisory
Cryostat 2 on RHEL 8cryostat-tech-preview/cryostat-grafana-dashboard-rhel8:2.4.0-7RHSA-2024:2088
HawtIO 4.0.0 for Red Hat build of Apache Camel 4netty-codec-httpRHSA-2024:3550
Migration Toolkit for Runtimes 1 on RHEL 8netty-codec-httpRHSA-2024:6657
Red Hat AMQ Broker 7netty-codec-httpRHSA-2024:2945
Red Hat AMQ Streams 2.7.0netty-codec-httpRHSA-2024:3527
Red Hat build of Apache Camel 4.4.1 for Spring Boot 3.2see advisoryRHSA-2024:4884
Red Hat build of Quarkus 3.2.12.Finalio.netty/netty-codec-http:4.1.108.Final-redhat-00001RHSA-2024:2705
Red Hat build of Quarkus 3.8.4.redhatio.netty/netty-codec-http:4.1.108.Final-redhat-00001RHSA-2024:2106

Frequently Asked Questions

### Summary The `HttpPostRequestDecoder` can be tricked to accumulate data. I have spotted currently two attack vectors ### Details 1. While the decoder can store items on the disk if configured so, there are no limits to the number of fields the form can have, an attacher can send a chunked post consisting of many small fields that will be accumulated in the `bodyListHttpData` list. 2. The decoder cumulates bytes in the `undecodedChunk` buffer until it can decode a field, this field can cumulate data without limits ### PoC Here is a Netty branch that provides a fix + tests : https://githu
O3 Security · Impact-Aware SCA

Is GHSA-5jpm-x58v-624v in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Netty's HttpPostRequestDecoder can OOM (Medium 5.3)