CVE-2026-40980: Spring AI · Uncontrolled Resource Consumption
Affects Spring AISource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium : upgrade to 1.1.5 or 1.0.6 when convenient.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.1.5, 1.0.6
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 28 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade Spring AI to 1.1.5 or 1.0.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SpringSpring AI | Affected
| Fixed in
|
| SpringSpring AI | Affected
| Fixed in
|
AI-suggested
Upgrading to Spring AI versions 1.0.6 or 1.1.5 or later resolves this vulnerability. Since the vendor has released fixed versions, applying these official patches is the recommended remediation. No temporary or alternative mitigations are indicated.
Description
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)