Spring Framework Denial of Service via AntPathMatcher

Exploitation

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

CVSS

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

EPSS

• CVE-2026-41848: 0.34% estimated exploitation activity in the next 30 days; percentile 26.93 (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 may be vulnerable to a Regular Expression Denial of Service (ReDoS) attack if an attacker is able to provide a pattern which is then directly or indirectly supplied to one of the following methods in AntPathMatcher: match(String pattern, String path), matchStart(String pattern, String path), extractUriTemplateVariables(String pattern, String path). Affected versions: Spring Framework 7.0.0 through 7.0.7; 6.2.0 through 6.2.18; 6.1.0 through 6.1.27; 5.3.0 through 5.3.48.

Published by the source

9 Jun 2026, 06:31 UTC

Last modified by the source

30 Jul 2026, 18:29 UTC

Source last checked

26 Oct 2026, 16:54 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-659m-px2c-25wj

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

# Patch Next advisory brief: CVE-2026-41848

Advisory: Spring Framework Denial of Service via AntPathMatcher
IDs: CVE-2026-41848, GHSA-659m-px2c-25wj
Record: https://patchnext.com/advisories/cve-2026-41848 (revision 1, source checked 26 Oct 2026, 16:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: org.springframework:spring-core 7.0.8, 6.2.19. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.springframework:spring-core: affected >= 7.0.0, <= 7.0.7; >= 6.2.0, <= 6.2.18; >= 6.1.0, <= 6.1.21; <= 5.3.39; fixed in 7.0.8, 6.2.19

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

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.springframework:spring-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-659m-px2c-25wj (GitHub-reviewed advisory GHSA-659m-px2c-25wj lists affected ranges: Maven org.springframework:spring-core >=7.0.0 =6.2.0 =6.1.0 =0 <=5.3.39)

Commands are suggestions: review each one before running it.