CVE-2026-40980 json
Spring AI Vulnerable to OOM by attacker-controlled PDF
published 6mo ago modified 14d ago also GHSA-26gg-9gv2-v27j , EUVD-2026-26013
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 15%
- public exploits
- 0
- none known
Summary
In Spring AI, a malicious PDF file can be crafted that triggers the allocation of unreasonable amounts of memory when handled by `ForkPDFLayoutTextStripper`.
Affected versions: Spring AI: 1.0.0 - 1.0.5 (fixed in 1.0.6), 1.1.0 - 1.1.4 (fixed in 1.1.5)
Patch / fix
- maven org.springframework.ai:spring-ai-pdf-document-reader 1.0.6, 1.1.5
- Spring Spring AI 1.0.6, 1.1.5
Is CVE-2026-40980 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 6mo ago
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.springframework.ai:spring-ai-pdf-document-reader | >=1.0.0, <1.0.6 >=1.1.0, <1.1.5 |
1.0.6 1.1.5 |
Affected products
- Spring Spring AI
Classification
- Weakness
-
- CWE-400 Uncontrolled Resource Consumption
References
-
spring.io
/security/cve-2026-40980
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-40980
advisory
-
github.com
/spring-projects/spring-ai
package
Sources
- CVE List CVE-2026-40980
- GitHub Advisory GHSA-26gg-9gv2-v27j
- NVD CVE-2026-40980
Fencer Intel 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.