What is the CVSS score of EUVD-2026-66821?

EUVD-2026-66821 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. EPSS exploitation probability: 0.3%.

How to fix or mitigate EUVD-2026-66821?

Within 24 hours, identify all internal applications using Spring AI versions 1.0.x, 1.1.x, or 2.0.0 and assess their exposure to untrusted PDF inputs. Implement immediate mitigations including request timeout limits (recommend 30-60 second timeouts), restrict PDF uploads to authenticated users only, and enable monitoring for StackOverflowError exceptions in application logs. Within 7 days, deploy input validation to reject PDFs exceeding reasonable nesting depth (recommend maximum 20-30 nested levels), implement resource limits on document processing threads, and establish alerting for repeated processing failures. Within 30 days, monitor Spring AI vendor communications for security patches; evaluate alternative document processing libraries as a longer-term solution and prepare migration planning; continue enforcement of interim mitigations and document any application-specific workarounds discovered.

Spring AI EUVD-2026-66821

| CVE-2026-47851 HIGH

Uncontrolled Recursion (CWE-674)

2026-08-26 vmware

GHSA-3934-8pqh-qq29

Buffer Overflow Java Spring Spring Ai

7.5

CVSS 3.1 · Vendor: vmware

View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

Access

Craft PDF with cyclic/deep TOC
Delivery

Submit PDF to ingestion endpoint
Exploit

Parser recurses without bound
Execution

JVM stack exhausted
Persist

StackOverflowError crashes ingestion thread
Impact

Document processing unavailable

Vulnerability Assessment

Weakness	CWE CWE-674
Exploitation Conditions	The application must be using Spring AI versions 1.0.0-1.0.9, 1.1.0-1.1.8, or 2.0.0 and must have an active PDF document ingestion pathway - this vulnerability is specific to PDF processing and does not affect other document types. The CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates that no authentication is required and no special network position is needed, meaning any attacker who can submit a PDF to the ingestion endpoint can trigger the flaw. What limits exploitation: the application must actually invoke Spring AI's PDF ingestion functionality; deployments that do not process PDFs, or that only ingest PDFs from fully trusted internal sources, are not exposed. The crash affects the ingestion thread specifically, so the scope of disruption depends on whether the application isolates ingestion threads from other service functions.
Impact	CVSS 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) accurately reflects a remotely exploitable, low-complexity denial of service. The network vector is valid because Spring AI ingestion endpoints can accept externally supplied documents in typical RAG deployments. EPSS data is not available in the provided intelligence, and the vulnerability has no KEV listing and no known public exploit code, making active exploitation speculative at this time. Real-world priority depends heavily on deployment architecture: applications that accept PDF uploads from untrusted users are meaningfully at risk of availability disruption, while internal-only document pipelines where PDF sources are controlled face substantially lower exposure. The impact is bounded to availability - confidentiality and integrity are unaffected. The primary concern is whether a crash of the ingestion thread is recoverable without service restart, which determines whether a single crafted PDF constitutes a persistent or transient denial of service.
Exploit ScenarioDerived	An attacker targeting a Spring AI-based RAG application that exposes a document upload endpoint crafts a PDF file containing a table of contents with thousands of nested levels or a cyclic reference loop. Submitting this file to the ingestion API causes the PDF parser to recurse without bound, overflowing the JVM thread stack and crashing the ingestion thread. Repeated submissions can sustain the denial of service condition, preventing legitimate document processing.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).

No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 27, 2026

Denial of service in Spring AI's PDF document ingestion crashes the processing thread when parsing a crafted PDF with a deeply nested or cyclic table of contents structure. Affected versions span the 1.0.x and 1.1.x release lines as well as the 2.0.0 release. An unauthenticated remote attacker who can supply a malicious PDF to an application's ingestion pipeline can trigger a StackOverflowError, halting document processing availability with no confidentiality or integrity impact. No public exploit code or CISA KEV listing has been identified at time of analysis.

RemediationAI

Consult the vendor advisory at https://spring.io/security/cve-2026-47851 for the specific patched version; the advisory has been published by VMware/Spring but exact fix version numbers are not independently confirmed in the available intelligence data - do not upgrade to an unconfirmed version. As a compensating control while patch testing proceeds, restrict PDF ingestion to trusted internal sources only, rejecting or sandboxing PDFs from external or untrusted origins. Additionally, consider wrapping the PDF ingestion call in a separate worker thread with a bounded stack size and exception handler so a StackOverflowError terminates only the worker rather than the ingestion service process. This adds implementation complexity but prevents full service disruption. Input validation at the document intake layer (e.g., rejecting PDFs whose TOC depth exceeds a configurable threshold) is another targeted mitigation if the parsing library exposes such controls.

Affected VersionsENISA

Spring AI 1.0.0 ≤1.0.9

Spring AI 1.1.0 ≤1.1.8

Spring AI 2.0.0

Affected Packages

euvd spring_ai no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Spring AI is a Java framework from VMware/Spring that provides abstractions for building AI-powered applications, including document ingestion pipelines for RAG (Retrieval-Augmented Generation) workflows. The affected code path involves PDF parsing, specifically processing the document's table of contents (TOC) structure. A cyclic or excessively deep TOC triggers unbounded recursion in the parser, exhausting the JVM thread stack and raising a StackOverflowError. This is characteristic of CWE-674 (Uncontrolled Recursion), though NVD has not assigned a formal CWE. The affected CPE is cpe:2.3:a:spring:spring_ai, covering all minor versions in the 1.0.x, 1.1.x, and 2.0.0 lines. The ingestion thread crash implies the StackOverflowError is not caught and handled gracefully, causing a thread-level availability failure rather than a simple processing error.

Know when Spring gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

Vendor (vmware) PRIMARY 7.5 HIGH

AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

vuln.today AI 7.5 HIGH

Network-reachable PDF ingestion endpoint requires no authentication; sole impact is availability via thread crash, with no confidentiality or integrity effect.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (vmware).

CVSS VectorVendor: vmware

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

DescriptionCVE.org

Analyzing a PDF with a deeply nested or cyclic table of contents can cause a StackOverflowError in the ingestion thread. Spring AI 2.0.0 Spring AI 1.1.0 - 1.1.8 Spring AI 1.0.0 - 1.0.9

Articles & Coverage 1

News 6 New Java Vulnerabilities - 6 High Severity, 1 With POC Aug 27, 2026

Executive ViewAI

Why It Matters

Spring AI versions 1.0.x, 1.1.x, and 2.0.0 contain a denial-of-service vulnerability in PDF document ingestion that can crash processing threads when handling malicious PDFs, directly impacting any application that relies on this library for document processing. An unauthenticated attacker with the ability to supply PDFs to the ingestion pipeline can halt document availability, disrupting workflow and potentially affecting time-sensitive business processes dependent on document processing.

Business Impact: High

Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include: (1) enforcing request timeouts on PDF processing operations to prevent thread starvation, (2) implementing PDF input validation to reject files with excessive table of contents nesting depth, (3) restricting PDF uploads to authenticated users and trusted sources only, (4) deploying application monitoring to detect and alert on StackOverflowError exceptions, and (5) implementing resource limits and circuit breakers to gracefully degrade service rather than crash.

Threat Intelligence Overview

EPSS Score

0.3%

Top 82% exploitable

Prevalence

Medium

growing but not yet ubiquitous Java AI framework

Data Quality

6 sources

Confidence: High

EUVD 🇯🇵JVN

NVD

CVE.org

EPSS

Vulnrichment

VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity HIGH

CISA KEV No

Public POC No

EPSS 0.3%

Patch available No

Active threat No

Deciding rule

HIGH severity (CVSS 7.0-8.9)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision

Scheduled

Exploitation

None

System Exposure· derived

Open

Automatable

Yes

Human Impact

High

Technical Impact

Partial

Priority Score

Low Medium High Critical

KEV: 0

EPSS: 0

CVSS: +38

PoC: 0

Weaponized: 0

Threat intel: 0

Gov advisory: 0

Attack Technique

Buffer Overflow HIGH

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.