Skip to content
Fencer Vulns
high 7.5

CVE-2026-41007 json

Spring HATEOAS heap exhaustion through unbounded internal caching

published 2026-06-09 5 mo ago modified 2026-07-29 3 mo ago also GHSA-439x-6767-44cv , EUVD-2026-35346

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 22%
public exploits
0
none known

Summary

Spring HATEOAS maintains an unbounded static cache of StringLinkRelation instances keyed on attacker-supplied strings.

Affected versions: Spring HATEOAS 1.5.0 through 1.5.6; 2.3.0 through 2.3.4; 2.4.0 through 2.4.1; 2.5.0 through 2.5.2; 3.0.0 through 3.0.3.

Patch / fix

  • maven org.springframework.hateoas:spring-hateoas 2.5.3, 3.0.4
  • Spring Spring HATEOAS 1.5.7, 2.3.5, 2.4.2, 2.5.2.1, 3.0.3.1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-41007 updated cvss 7.5

spring-hateoas: Spring HATEOAS: Denial of Service via unbounded static cache

  • Red Hat Fuse 7 spring-hateoas
    affected: workaround, no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
5 mo ago

Exploit prediction

0.30% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
maven org.springframework.hateoas:spring-hateoas
>=3.0.0, <3.0.4
>=2.5.0, <2.5.3
>=2.3.0, <=2.3.4
<=1.5.6
>=2.4.0, <=2.4.1
3.0.4
2.5.3

Affected products

  • Spring Spring HATEOAS

Classification

Weakness
  • CWE-770 Allocation of Resources Without Limits or Throttling

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.