# CVE-2026-41007: Spring HATEOAS heap exhaustion through unbounded internal caching

> Attackers can cause heap exhaustion and denial of service by exploiting unbounded caching in Spring HATEOAS.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Jun 2026
- **Updated:** 27 Jun 2026
- **Also known as:** CLSA-2026-1786568979, CLSA-2026-1791959812, GHSA-439x-6767-44cv, ROOT-APP-MAVEN-CVE-2026-41007

## What is CVE-2026-41007?

CVE-2026-41007 is a high-severity denial of service vulnerability in Spring HATEOAS, published on 9 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2026-41007?

10 open source packages ship an affected version, including org.springframework.hateoas:spring-hateoas. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.springframework.hateoas:spring-hateoas` | Maven | All versions to 1.5.6 | None |
| `org.springframework.hateoas:spring-hateoas` | Maven | All versions to 1.5.6 | None |
| `org.springframework.hateoas:spring-hateoas` | Maven | From 2.3.0 to 2.3.4 | None |
| `org.springframework.hateoas:spring-hateoas` | Maven | From 2.3.0 to 2.3.4 | None |
| `org.springframework.hateoas:spring-hateoas` | Maven | From 2.4.0 to 2.4.1 | None |
| `org.springframework.hateoas:spring-hateoas` | Maven | From 2.4.0 to 2.4.1 | None |
| `org.springframework.hateoas:spring-hateoas` | Maven | From 2.5.0 | 2.5.3 |
| `org.springframework.hateoas:spring-hateoas` | Maven | From 2.5.0 | 2.5.3 |
| `org.springframework.hateoas:spring-hateoas` | Maven | From 3.0.0 | 3.0.4 |
| `org.springframework.hateoas:spring-hateoas` | Maven | From 3.0.0 | 3.0.4 |

Products: Vmware Spring Hateoas.

## How do I fix CVE-2026-41007?

Upgrade org.springframework.hateoas:spring-hateoas to a fixed version for your release line: 2.5.3 or 3.0.4.

## Is CVE-2026-41007 being exploited?

There is no known exploitation of CVE-2026-41007 in the wild and no public exploit code.

## Other vulnerabilities in Spring HATEOAS

- [CVE-2026-41006](https://insights.sbomify.com/CVE-2026-41006/): Spring HATEOAS Collection+JSON/UBER deserializers do not honor Jackson configuration (high 7.5)
- [CVE-2023-34036](https://insights.sbomify.com/CVE-2023-34036/): Forwarded header exploit with Spring HATEOAS on WebFlux (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41007 and fix it if it is affected.

What it is: CVE-2026-41007 is a high-severity denial of service vulnerability in Spring HATEOAS, published on 9 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-41007 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.springframework.hateoas:spring-hateoas (Maven): affected all versions up to 1.5.6; no fix listed
- org.springframework.hateoas:spring-hateoas (Maven): affected all versions up to 1.5.6; no fix listed
- org.springframework.hateoas:spring-hateoas (Maven): affected from 2.3.0 up to 2.3.4; no fix listed
- org.springframework.hateoas:spring-hateoas (Maven): affected from 2.3.0 up to 2.3.4; no fix listed
- org.springframework.hateoas:spring-hateoas (Maven): affected from 2.4.0 up to 2.4.1; no fix listed
- org.springframework.hateoas:spring-hateoas (Maven): affected from 2.4.0 up to 2.4.1; no fix listed
- org.springframework.hateoas:spring-hateoas (Maven): affected from 2.5.0; fixed in 2.5.3
- org.springframework.hateoas:spring-hateoas (Maven): affected from 2.5.0; fixed in 2.5.3
- org.springframework.hateoas:spring-hateoas (Maven): affected from 3.0.0; fixed in 3.0.4
- org.springframework.hateoas:spring-hateoas (Maven): affected from 3.0.0; fixed in 3.0.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41007/ (Markdown: https://insights.sbomify.com/CVE-2026-41007/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41007
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41007
- OSV: https://osv.dev/vulnerability/CVE-2026-41007

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41007/
Summaries are generated and may contain mistakes; the official description above is the record.
