dbcve.org
Spring AiFramework / library · VMware

CVE-2026-40966

MEDIUM · 5.9 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 →
68/100
Remediation priority · Elevated
Remotely reachable No privileges 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, an attacker can bypass conversation isolation and exfiltrate sensitive memory from other users’ chat histories, including secrets and credentials, by injecting filter logic through conversationId. Only applications that use VectorStoreChatMemoryAdvisor and pass user-supplied input as a conversationId are affected.

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 · moderate confidence

This is an input validation vulnerability in Spring AI's VectorStoreChatMemoryAdvisor where user-supplied conversationId values are not properly sanitized, allowing attackers to inject filter logic that bypasses conversation isolation. This enables unauthorized access to other users' chat histories and exfiltration of sensitive data including secrets and credentials.

MitigationImplement strict input validation on the conversationId parameter to reject any injected filter logic, and use system-generated conversation identifiers instead of allowing user-supplied values to ensure proper session isolation.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Check installed Spring AI version
    Locate the spring-ai-core or spring-ai dependency in your build configuration (pom.xml, build.gradle, or equivalent) and note the exact version number
    Affected if Version is >= 1.0.0 and < 1.0.6, or >= 1.1.0 and < 1.1.5
  2. Verify VectorStoreChatMemoryAdvisor is in use
    Search your codebase for imports or references to org.springframework.ai.chat.memory.advisor.VectorStoreChatMemoryAdvisor or usage of VectorStoreChatMemoryAdvisor in your chat configuration
    Affected if This advisor class is being used in your application
  3. Inspect conversationId parameter handling
    Review the code that accepts or processes the conversationId parameter in your chat memory implementation; check if the value is passed directly to VectorStoreChatMemoryAdvisor without sanitization
    Affected if User-supplied conversationId values are accepted and used without validation or sanitization
  4. Check for input validation on conversationId
    Search for any input validation, allowlist, or sanitization logic applied to the conversationId parameter before it is used in filter or query operations
    Affected if No input validation exists on conversationId, or validation can be bypassed by injected filter syntax

Your environment is affected if you are running a vulnerable Spring AI version AND using VectorStoreChatMemoryAdvisor with user-supplied conversationId values that lack strict input validation.

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

Implement strict input validation on the conversationId parameter to reject any injected filter logic, and use system-generated conversation identifiers instead of allowing user-supplied values to ensure proper session isolation.

Recommended fix Moderate confidence

Spring AI 1.0.6 or 1.1.5 (or later)

  1. Identify all Spring AI applications that use VectorStoreChatMemoryAdvisor
  2. Audit code to determine if user-supplied input is being passed directly as the conversationId parameter
  3. If user-supplied conversationId is used, temporarily implement server-side validation to only allow alphanumeric IDs or UUIDs
  4. Upgrade Spring AI dependency to version 1.0.6 or later for the 1.0.x line, or 1.1.5 or later for the 1.1.x line
  5. After upgrade, verify conversation isolation by testing that one user's conversationId cannot access another user's chat history
  6. If using Maven, update the spring-ai-core dependency version; if using Gradle, update the spring-ai-core plugin version
Caveat Review Spring AI release notes for the 1.0.6 and 1.1.5 releases for any API changes that may affect compatibility with existing application code

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

Fix this in Spring Ai Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40966 — 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-40966 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