Spring Framework URL Parsing with Host Validation

Exploitation

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

CVSS

8.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

EPSS

• CVE-2024-22262: 1.19% estimated exploitation activity in the next 30 days; percentile 68.00 (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.

Applications that use UriComponentsBuilder to parse an externally provided URL (e.g. through a query parameter) AND perform validation checks on the host of the parsed URL may be vulnerable to a open redirect https://cwe.mitre.org/data/definitions/601.html attack or to a SSRF attack if the URL is used after passing validation checks. This is the same as CVE-2024-22259 https://spring.io/security/cve-2024-22259 and CVE-2024-22243 https://spring.io/security/cve-2024-22243 , but with different input.

Published by the source

16 Apr 2024, 06:30 UTC

Last modified by the source

13 Feb 2025, 19:00 UTC

Source last checked

26 Oct 2026, 16:34 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-2wrp-6fg6-hmc5

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

# Patch Next advisory brief: CVE-2024-22262

Advisory: Spring Framework URL Parsing with Host Validation
IDs: CVE-2024-22262, GHSA-2wrp-6fg6-hmc5
Record: https://patchnext.com/advisories/cve-2024-22262 (revision 1, source checked 26 Oct 2026, 16:34 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.springframework:spring-web 6.1.6, 6.0.19, 5.3.34. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.springframework:spring-web: affected < 5.3.34; >= 6.0.0, < 6.0.19; >= 6.1.0, < 6.1.6; fixed in 6.0.19, 6.1.6, 5.3.34

## Suggested inspection (read-only)
- Maven org.springframework:spring-web: 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 org.springframework:spring-web.
- 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-2wrp-6fg6-hmc5 (GitHub-reviewed advisory GHSA-2wrp-6fg6-hmc5 lists affected ranges: Maven org.springframework:spring-web >=0 =6.0.0 =6.1.0 <6.1.6)

Commands are suggestions: review each one before running it.