cve.bz

CVE-2026-41007 vmware spring hateoas

7.5 highEPSS 0.3%Fix available

High (7.5) in vmware spring hateoas. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in org.springframework.hateoas:spring-hateoas 2.5.3, 3.0.4.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 23rd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-06-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-770 Allocation of Resources Without Limits or Throttling
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-41007 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-41007?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-41007?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-41007 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Spring HATEOASfrom 1.5.0 before 1.5.7
Spring HATEOASfrom 2.3.0 before 2.3.5
Spring HATEOASfrom 2.4.0 before 2.4.2
Spring HATEOASfrom 2.5.0 before 2.5.2.1
Spring HATEOASfrom 3.0.0 before 3.0.3.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-439x-6767-44cvMavenorg.springframework.hateoas:spring-hateoas>=3.0.0 <3.0.43.0.4
GHSA-439x-6767-44cvMavenorg.springframework.hateoas:spring-hateoas>=2.5.0 <2.5.32.5.3
GHSA-439x-6767-44cvMavenorg.springframework.hateoas:spring-hateoas>=2.3.0 <=2.3.4no fix published
GHSA-439x-6767-44cvMavenorg.springframework.hateoas:spring-hateoas<=1.5.6no fix published
GHSA-439x-6767-44cvMavenorg.springframework.hateoas:spring-hateoas>=2.4.0 <=2.4.1no fix published

Red Hat

Red Hat rates this Important.

Red Hat's statement

This is an Important denial of service flaw in Spring HATEOAS, affecting Red Hat JBoss Fuse. The vulnerability arises from an unbounded static cache that can be exhausted by attacker-supplied strings, leading to resource unavailability. This impact is considered Important due to the potential for remote, unauthenticated attackers to disrupt service.

Red Hat's mitigation

To mitigate the risk of denial of service, restrict network access to applications that use Spring HATEOAS to trusted clients and networks. Implementing rate limiting on incoming requests can also help reduce the impact by limiting the volume of attacker-supplied strings that can trigger cache exhaustion. Ensure that any changes to network configurations are thoroughly tested to avoid disrupting legitimate service.

ProductPackageStateAdvisory
Red Hat Fuse 7spring-hateoasFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-41007.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).

References

Check your stackJSON