Undertow vulnerable to Request Smuggling

Exploitation

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

CVSS

6.1 · CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

EPSS

• CVE-2017-7559: 1.91% estimated exploitation activity in the next 30 days; percentile 79.83 (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.

In Undertow 2.x before 2.0.0.Alpha2, 1.4.x before 1.4.17.Final, and 1.3.x before 1.3.31.Final, it was found that the fix for CVE-2017-2666 was incomplete and invalid characters are still allowed in the query string and path parameters. This could be exploited, in conjunction with a proxy that also permitted the invalid characters but with a different interpretation, to inject data into the HTTP response. By manipulating the HTTP response the attacker could poison a web-cache, perform an XSS attack, or obtain sensitive information from requests other than their own.

Published by the source

13 May 2022, 01:36 UTC

Last modified by the source

29 Jan 2023, 05:04 UTC

Source last checked

26 Oct 2026, 16:02 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-rj76-h87p-r3wf

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

# Patch Next advisory brief: CVE-2017-7559

Advisory: Undertow vulnerable to Request Smuggling
IDs: CVE-2017-7559, GHSA-rj76-h87p-r3wf
Record: https://patchnext.com/advisories/cve-2017-7559 (revision 1, source checked 26 Oct 2026, 16:02 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.1)
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.0.0.Alpha2, 1.4.17.Final, 1.3.31.Final. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven io.undertow:undertow-core: affected >= 1.4.0, < 1.4.17.Final; >= 1.3.0, < 1.3.31.Final; >= 2.0.0.Alpha1, <= 2.0.0.Alpha1; fixed in 1.4.17.Final, 2.0.0.Alpha2, 1.3.31.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-rj76-h87p-r3wf (GitHub-reviewed advisory GHSA-rj76-h87p-r3wf lists affected ranges: Maven io.undertow:undertow-core >=1.4.0 =1.3.0 =2.0.0.Alpha1 <=2.0.0.Alpha1)

Commands are suggestions: review each one before running it.