Undertow Missing Release of Memory after Effective Lifetime vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.3 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2024-3653: 1.87% estimated exploitation activity in the next 30 days; percentile 79.32 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

A vulnerability was found in Undertow. This issue requires enabling the learning-push handler in the server's config, which is disabled by default, leaving the maxAge config in the handler unconfigured. The default is -1, which makes the handler vulnerable. If someone overwrites that config, the server is not subject to the attack. The attacker needs to be able to reach the server with a normal HTTP request.

Published by the source

9 Jul 2024, 00:31 UTC

Last modified by the source

4 Nov 2024, 22:22 UTC

Source last checked

26 Oct 2026, 16:31 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-ch7q-gpff-h9hp

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-3653

Advisory: Undertow Missing Release of Memory after Effective Lifetime vulnerability
IDs: CVE-2024-3653, GHSA-ch7q-gpff-h9hp
Record: https://patchnext.com/advisories/cve-2024-3653 (revision 1, source checked 26 Oct 2026, 16:31 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: io.undertow:undertow-core 2.3.15.Final, 2.2.34.Final. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven io.undertow:undertow-core: affected >= 2.3.0.Alpha1, < 2.3.15.Final; < 2.2.34.Final; fixed in 2.3.15.Final, 2.2.34.Final

## Suggested inspection (read-only)
- Maven io.undertow:undertow-core: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on io.undertow:undertow-core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-ch7q-gpff-h9hp (GitHub-reviewed advisory GHSA-ch7q-gpff-h9hp lists affected ranges: Maven io.undertow:undertow-core >=2.3.0.Alpha1 =0 <2.2.34.Final)

Commands are suggestions: review each one before running it.