Skip to content

← Actionable
High, CVSS 7.5

Spring Data Commons: Heap exhaustion from unbounded property-lookup cache retaining crafted string keys

CVE-2026-41716GHSA-9fw2-h3hf-293r

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

  • GitHub Advisory Database and maintainer security advisories on GitHub

    GitHub-reviewed advisory GHSA-9fw2-h3hf-293r lists affected ranges: Maven org.springframework.data:spring-data-commons >=4.0.0 =3.5.0 =3.4.0 =3.3.0 =0 <=2.7.19

    VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
  • CVE-2026-41716: 0.36% estimated exploitation activity in the next 30 days; percentile 30.22 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Spring Data's internal property-lookup cache accepts and permanently retains attacker-supplied strings as cache keys, allowing heap exhaustion through repeated requests. Affected versions: Spring Data Commons 2.7.0 through 2.7.19; 3.3.0 through 3.3.16; 3.4.0 through 3.4.14; 3.5.0 through 3.5.11; 4.0.0 through 4.0.5.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-9fw2-h3hf-293r

Agent brief

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

# Patch Next advisory brief: CVE-2026-41716

Advisory: Spring Data Commons: Heap exhaustion from unbounded property-lookup cache retaining crafted string keys
IDs: CVE-2026-41716, GHSA-9fw2-h3hf-293r
Record: https://patchnext.com/advisories/cve-2026-41716 (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: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: org.springframework.data:spring-data-commons 4.0.6, 3.5.12. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.springframework.data:spring-data-commons: affected >= 4.0.0, <= 4.0.5; >= 3.5.0, <= 3.5.11; >= 3.4.0, <= 3.4.14; >= 3.3.0, <= 3.3.16; <= 2.7.19; fixed in 4.0.6, 3.5.12

## Suggested inspection (read-only)
- Maven org.springframework.data:spring-data-commons: 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.data:spring-data-commons.
- 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-9fw2-h3hf-293r (GitHub-reviewed advisory GHSA-9fw2-h3hf-293r lists affected ranges: Maven org.springframework.data:spring-data-commons >=4.0.0 =3.5.0 =3.4.0 =3.3.0 =0 <=2.7.19)

Commands are suggestions: review each one before running it.

Loading voting…