dbcve.org
Spring AiFramework / library · VMware

CVE-2026-40980

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-28
Fix available
A fix is available. Upgrade to 1.0.6 / 1.1.5 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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)

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Spring AI's `ForkPDFLayoutTextStripper` component allocates memory based on PDF content without proper bounds checking. A malicious PDF can trigger unreasonable memory allocation, leading to resource exhaustion and potential denial of service. This is a classic resource exhaustion (memory) vulnerability in PDF text extraction functionality.

MitigationUpgrade Spring AI to version 1.0.6 or 1.1.5 or later. If immediate patching is not possible, limit or validate PDF files processed by the application, and implement memory usage monitoring to detect anomalous consumption.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Spring AiFramework / library
Affected:>= 1.0.0, < 1.0.6>= 1.1.0, < 1.1.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Spring AI installation and version
    Locate the Spring AI dependency in your project build file (pom.xml, build.gradle, or similar) or check the application's classpath for the spring-ai-core or spring-ai-pdf library jar and note its version number
    Affected if The installed version falls within >= 1.0.0 and < 1.0.6, or >= 1.1.0 and < 1.1.5
  2. Verify PDF processing is in use
    Search your codebase for imports or references to ForkPDFLayoutTextStripper, or any PDF text extraction functionality from Spring AI
    Affected if Your application code or dependencies use ForkPDFLayoutTextStripper or PDF layout parsing from Spring AI
  3. Check if PDF input is user-controlled
    Review your application's endpoints or services that accept PDF files and determine whether external or untrusted PDF files can be passed to the PDF processing component
    Affected if Your application accepts PDF files from external sources without strict validation before processing them with Spring AI
  4. Review memory configuration
    Check your JVM or container memory settings (Xmx, container limits) and whether there are any resource limits configured for PDF processing operations
    Affected if Memory limits are not set or are set very high, allowing potential unbounded allocation

You are affected if your Spring AI version is 1.0.0 through 1.0.5 or 1.1.0 through 1.1.4 AND your application uses ForkPDFLayoutTextStripper to process potentially untrusted PDF files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.0.6 / 1.1.5 or later
Fixed in 1.0.61.1.5
Interim mitigation

Upgrade Spring AI to version 1.0.6 or 1.1.5 or later. If immediate patching is not possible, limit or validate PDF files processed by the application, and implement memory usage monitoring to detect anomalous consumption.

Recommended fix High confidence

Spring AI 1.0.6 or 1.1.5 (depending on current major version)

  1. Identify the current Spring AI version in the project (check pom.xml, build.gradle, or dependencies)
  2. If currently on Spring AI 1.0.x, upgrade to version 1.0.6
  3. If currently on Spring AI 1.1.x, upgrade to version 1.1.5
  4. Update the version in the project's dependency management file (pom.xml, build.gradle, or similar)
  5. Run build/compile to verify the upgrade succeeds
  6. Review Spring AI 1.0.6 and 1.1.5 release notes for any required code adjustments
Caveat Check release notes for breaking changes between versions; minor version upgrades typically have minimal compatibility issues

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Spring Ai Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing8.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,140
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40980 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-40980 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data