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

CVE-2024-7885 — undertow-core

HIGHFix: undertow-io/undertow@ce5182c

CVE-2024-7885 is a high-severity (CVSS 7.5) CWE-362 vulnerability in io.undertow:undertow-core. A fix is available for io.undertow:undertow-core — see the affected versions and patch details below.

Undertow: improper state management in proxy protocol parsing causes information leakage

Also known asGHSA-9623-mqmm-5rcf
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-7885.

EPSS Exploitation Probability

via FIRST.org ↗
2.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs86th percentile — riskier than 86% of all scored CVEsHighest risk
0.23%4.52%8.82%13.1%10.7%2.6%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

2 pkgs affected
☕io.undertow:undertow-core☕io.undertow:undertow-core

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

A vulnerability was found in Undertow where the ProxyProtocolReadListener reuses the same StringBuilder instance across multiple requests. This issue occurs when the parseProxyProtocolV1 method processes multiple requests on the same HTTP connection. As a result, different requests may share the same StringBuilder instance, potentially leading to information leakage between requests or responses. In some cases, a value from a previous request or response may be erroneously reused, which could lead to unintended data exposure. This issue primarily results in errors and connection termination but creates a risk of data leakage in multi-request environments.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenio.undertow:undertow-coreall versions2.2.36.Finalio.undertow:undertow-core:2.2.36.Final
☕Mavenio.undertow:undertow-core≥ 2.3.0.Alpha1&&< 2.3.17.Final2.3.17.Finalio.undertow:undertow-core:2.3.17.Final

Affected Products

9 products · 10 configurations
Application
build of apache camel - hawtioredhat
all
Application
build of apache camel for spring bootredhat
all
Application
build of keycloakredhat
all
Application
data gridredhat
1 version
8.0.0
Application
integration camel kredhat
all
Application
jboss enterprise application platformredhat
2 versions
7.0.08.0.0

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.undertow:undertow-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update io.undertow:undertow-core to 2.2.36.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-7885 is resolved across your whole dependency graph.

  3. 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

Red Hat decided to rate this vulnerability as Important because of the potential loss of Availability and no additional privileges being required.

ProductFixed inAdvisory
HawtIO 4.0.0 for Red Hat build of Apache Camel 4undertowRHSA-2024:11023
Red Hat build of Apache Camel 3.20.7 for Spring BootundertowRHSA-2024:6883
Red Hat build of Apache Camel 4.4.2 for Spring BootundertowRHSA-2024:6508
Red Hat JBoss Enterprise Application Platformio.undertow/undertow-core:2.2.33.SP2-redhat-00001RHSA-2024:8080
Red Hat JBoss Enterprise Application Platform 7see advisoryRHSA-2024:7735
Red Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7eap7-apache-commons-beanutils-0:1.11.0-1.redhat_00001.1.el7eapRHSA-2025:16667
Red Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7eap7-jackson-annotations-0:2.10.4-4.redhat_00008.1.el7eapRHSA-2026:0743
Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 8eap7-undertow-0:2.2.33-2.SP2_redhat_00001.1.el8eapRHSA-2024:7736

Frequently Asked Questions

A vulnerability was found in Undertow where the ProxyProtocolReadListener reuses the same StringBuilder instance across multiple requests. This issue occurs when the parseProxyProtocolV1 method processes multiple requests on the same HTTP connection. As a result, different requests may share the same StringBuilder instance, potentially leading to information leakage between requests or responses. In some cases, a value from a previous request or response may be erroneously reused, which could lead to unintended data exposure. This issue primarily results in errors and connection termination bu
O3 Security · Impact-Aware SCA

Is CVE-2024-7885 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2024-7885: undertow-core — Fixed in 2.2.36.Final