# CVE-2026-41849: Spring Framework Denial of Service via Integer Overflow in SpEL Expressions

> An attacker can cause a Denial of Service in Spring Framework by submitting a crafted SpEL expression that triggers an integer overflow and excessive resource consumption.

- **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:** 9 Jun 2026
- **Also known as:** CLEANSTART-2026-KM08371, CLSA-2026-1783558960, CLSA-2026-1783645376, CLSA-2026-1783645393, CLSA-2026-1787846138, DEBIAN-CVE-2026-41849, GHSA-775g-4xr8-78h8, ROOT-APP-MAVEN-CVE-2026-41849, UBUNTU-CVE-2026-41849

## What is CVE-2026-41849?

CVE-2026-41849 is a high-severity vulnerability in Vmware Spring Framework, published on 9 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An integer overflow vulnerability exists in the evaluation logic of the Spring Expression Language (SpEL). An attacker can exploit this by supplying a specially crafted SpEL expression that triggers excessive resource consumption, resulting in a Denial of Service (DoS).

Affected versions:
Spring Framework 5.3.0 through 5.3.48.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.springframework:spring-expression` | Maven | All versions to 5.3.39 | None |
| `org.springframework:spring-expression` | Maven | All versions to 5.3.39 | None |

Products: Vmware Spring Framework.

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

Upgrade to a fixed version.

## Is CVE-2026-41849 being exploited?

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

## Other vulnerabilities in Vmware Spring Framework

- [CVE-2026-47884](https://insights.sbomify.com/CVE-2026-47884/): Spring Framework Improper Path Limitation in XsltView (critical 9.8)
- [CVE-2026-47890](https://insights.sbomify.com/CVE-2026-47890/): Spring Framework Server Sent Event stream corruption while rendering fragments (critical 9.8)
- [CVE-2026-47891](https://insights.sbomify.com/CVE-2026-47891/): Spring Framework maxInMemorySize Bypassed in Jaxb2Decoder (critical 9.8)
- [CVE-2026-47892](https://insights.sbomify.com/CVE-2026-47892/): Spring Framework Header Predicate Bypass in WebFlux Functional Endpoints (critical 9.8)
- [CVE-2026-59313](https://insights.sbomify.com/CVE-2026-59313/): Server Sent Event stream corruption in Spring MVC functional web framework (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41849 is a high-severity vulnerability in Vmware Spring Framework, 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-41849 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.springframework:spring-expression (Maven): affected all versions up to 5.3.39; no fix listed
- org.springframework:spring-expression (Maven): affected all versions up to 5.3.39; no fix listed

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-41849/ (Markdown: https://insights.sbomify.com/CVE-2026-41849/index.md)
```

## Sources

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

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