CVE Watchtower

CVE-2026-59338Spring AI Uncontrolled Resource Consumption

Spring

Vulnerability Summary

Unbounded Tika text extraction can exhaust JVM memory. TikaDocumentReader in Spring AI uses Apache Tika to extract text from documents. Its default configuration disables Tika's built-in content-size limit, so the extracted text of a parsed document is buffered in memory with no absolute bound. Apache Tika still aborts a parse when the extracted text is disproportionate to the size of the input, which rejects highly compressed inputs such as archive bombs, but that guard is relative to the input and places no ceiling on the total amount of text extracted. An application that uses TikaDocumentReader to process documents from an untrusted source (e.g., user-uploaded files or attacker-supplied URLs) may therefore be induced to allocate an excessive amount of memory while parsing a sufficiently large document, potentially exhausting available JVM heap and causing a denial of service. Affected artifact: org.springframework.ai:spring-ai-tika-document-reader.
Severity Level
HIGH(7.5)
Published Date
Nov 19, 2026
Last Modified
Nov 19, 2026
Exploitation Status
No confirmed exploitation yet
CVE Record Status
Reserved
This CVE ID is referenced in a public advisory, but the CVE Program has not published its official CVE Record yet. Full CVSS/CPE data from NVD will appear here once it does.
Root Weakness (CWE)
The product does not properly control the allocation and maintenance of a limited resource, enabling denial-of-service conditions.
CVSS v3.1 Base Metrics — Score 7.5 (HIGH)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityNone
IntegrityNone
AvailabilityHigh

Affected & Patched Versions

Affected Versions
  • Spring AI 2.0.0 through 2.0.2
  • Spring AI 1.1.0 through 1.1.9
  • Spring AI 1.0.0 through 1.0.10
Patched Versions
  • Spring AI 2.0.3 (open source)
  • Spring AI 2.0.2.1 (commercial support only)
  • Spring AI 1.1.10 (commercial support only)
  • Spring AI 1.0.11 (commercial support only)

What to do

Plan remediation soon. No exploitation is confirmed yet, but the severity is high.

  1. Check whether you run Spring AI and which version.
  2. Update to a patched version listed above, then confirm the new version.

Timeline

  • Nov 19, 2026Published
  • Nov 19, 2026Record last modified

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get notified about new Spring AI CVEsYou are reading CVE-2026-59338. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

More Spring AI CVEs

External References

Data last checked: Nov 20, 2026 05:01 UTC