Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Medium · CVSS 6.5

How to Fix CVE-2026-40980: Spring AI (Bundle Sibling)

By Sai Kiran Pandrala

Last verified: 2026-05-25

CVE-2026-40980 is a sibling vulnerability in the same vendor advisory as CVE-2026-40967. Applying the patched build named in the primary write-up closes this CVE as well.

⚡ At a glance
SeverityCVSS 6.5 - Medium
Actively exploited?Not currently in CISA KEV
AffectedSame as the bundle - see CVE-2026-40967
Fixed inSame patched build as CVE-2026-40967 (See vendor advisory)
Type (CWE)CWE-400: CWE-400: Uncontrolled Resource Consumption

What's different about 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)

The technical impact and remediation are identical to the primary CVE in the bundle. The same vendor patch closes both.

How to fix CVE-2026-40980

Apply the patched build per the primary write-up: How to Fix CVE-2026-40967.

The patch installation procedure, verification commands, and interim mitigations are documented there. Reusing one runbook keeps the rollout consistent across the bundle.

Frequently asked questions

Is CVE-2026-40980 fixed by the same patch as CVE-2026-40967?

Yes. CVE-2026-40980 ships in the same vendor advisory as CVE-2026-40967. Applying the patched build named in the primary write-up closes both.

What is the CVSS score for CVE-2026-40980?

The CVSS base score is 6.5 (Medium).

Is it being exploited?

It is not currently listed in CISA KEV.

References


*Part of the Spring AI bundle. Full procedure at CVE-2026-40967.*