Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

GHSA-9fw2-h3hf-293r — spring-data-commons

HIGH

GHSA-9fw2-h3hf-293r is a high-severity (CVSS 7.5) CWE-770 vulnerability in org.springframework.data:spring-data-commons. A fix is available for org.springframework.data:spring-data-commons — see the affected versions and patch details below.

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

Also known asCVE-2026-41716
Published
Jun 10, 2026
Updated
Sep 10, 2026
Affected
5 pkgs
Patched
2 / 5
Exploits
None indexed
Exploitation data as of Sep 27, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-9fw2-h3hf-293r.

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs37th percentile — riskier than 37% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-9fw2-h3hf-293r by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

5 pkgs affected
☕org.springframework.data:spring-data-commons☕org.springframework.data:spring-data-commons☕org.springframework.data:spring-data-commons☕org.springframework.data:spring-data-commons☕org.springframework.data:spring-data-commons

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

5 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.springframework.data:spring-data-commons≥ 4.0.0&&< 4.0.64.0.6org.springframework.data:spring-data-commons:4.0.6
☕Mavenorg.springframework.data:spring-data-commons≥ 3.5.0&&< 3.5.123.5.12org.springframework.data:spring-data-commons:3.5.12
☕Mavenorg.springframework.data:spring-data-commons≥ 3.4.0No fix
☕Mavenorg.springframework.data:spring-data-commons≥ 3.3.0No fix
☕Mavenorg.springframework.data:spring-data-commonsall versionsNo fix

Affected Products

1 product · 5 configurations
Application
spring data commonsbroadcom
≥ 4.0.0 && < 4.0.5.1
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.data:spring-data-commons, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.springframework.data:spring-data-commons to 4.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9fw2-h3hf-293r is resolved across your whole dependency graph.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

A flaw was found in Spring Data Commons. The TypeDiscoverer cache can be exhausted by sending many unique invalid property names, leading to denial of service through excessive memory consumption. Red Hat products that bundle spring-data-commons and expose Spring Data query resolution to untrusted input are affected.…

Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Source: Red Hat security advisory for GHSA-9fw2-h3hf-293r (CC BY 4.0)
ProductFixed inAdvisory
Red Hat OpenShift Dev Spaces 3.30devspaces/openvsx-rhel9:1787759145RHSA-2026:62260

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-9fw2-h3hf-293r in your dependencies?

Find it across Maven, including transitive dependencies.

GHSA-9fw2-h3hf-293r: spring-data (High 7.5) | O3 Security