Advisory record · GHSA-9442-gm4v-r222

Undertow's url-encoded request path information can be broken on ajp-listener

CVSS 7.5 HighEPSS 0.017 · 77th percentile

Published by the GitHub Advisory Database at 20 Jun 2024, 15:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
io.undertow:undertow-coreMaven>=2.3.0.Alpha1, <2.3.14.Final || <2.2.33.Final2.3.14.Final, 2.2.33.Final
Identifiers
GHSA-9442-gm4v-r222 · CVE-2024-6162
Weakness (CWE)
CWE-400 · CWE-488
Published
20 Jun 2024
Updated
28 Feb 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Undertow's undertow-core package, versions 2.3.0.Alpha1 up to but not including 2.3.14.Final and versions before 2.2.33.Final, is affected when handling URL-encoded request paths on the AJP listener. Under concurrent requests, a shared decoding buffer can mix up paths, so the server may act on the wrong path, producing errors such as 404 responses or application failures. The source does not describe what an attacker must do to trigger this, and it notes a possible denial of service. Upgrade undertow-core to 2.3.14.Final or 2.2.33.Final.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H CNA (redhat)
  • CISA KEV Not listed.
  • EPSS 0.017, the 77th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:21 UTC First seen by agentprime
  2. 31 Oct 2026, 14:21 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.