CVE-2026-40980

CVE-2026-40980 is a medium-severity vulnerability in Vmware Spring Ai with a CVSS 3.x base score of 6.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-400.

Key facts

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)

Frequently asked questions

What is CVE-2026-40980?
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)
How severe is CVE-2026-40980?
CVE-2026-40980 has a CVSS 3.x base score of 6.5, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2026-40980 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (15th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-40980?
CVE-2026-40980 affects Vmware Spring Ai. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-40980?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-40980 have an EU (EUVD) identifier?
Yes. CVE-2026-40980 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-26013.
When was CVE-2026-40980 published?
CVE-2026-40980 was published on 2026-04-28 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Vmware Spring Ai

All CVEs affecting Vmware Spring Ai →

Other CWE-400 (Uncontrolled Resource Consumption) vulnerabilities

Browse all CWE-400 (Uncontrolled Resource Consumption) vulnerabilities →