dbcve.org
Spring AiFramework / library · VMware

CVE-2026-41712

HIGH · 7.5 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to 1.0.7 / 1.1.6 or later.
See remediation →
84/100
Remediation priority · High
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
Spring AI's chat memory component contained a problematic default that, when not explicitly overridden, could result in unintended data exposure between users.

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 chat memory component uses a problematic default configuration that fails to enforce proper user session isolation. When developers do not explicitly override this default, chat memory data can be inadvertently shared between different users, allowing one user to potentially access another user's conversation history.

MitigationReview all Spring AI chat memory implementations and explicitly configure user-specific memory isolation settings. Ensure that each user session has its own dedicated memory context that cannot be accessed by other users.

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.7>= 1.1.0, < 1.1.6

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

CVSS:3.1/AV:N/AC:L/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. Identify Spring AI version
    Check the Spring AI library version in your project dependencies (pom.xml, build.gradle, or JAR manifest). Compare against the affected ranges: 1.0.0 to 1.0.6, or 1.1.0 to 1.1.5.
    Affected if Your Spring AI version falls within 1.0.0-1.0.6 or 1.1.0-1.1.5
  2. Confirm chat memory feature is in use
    Review your codebase for usage of Spring AI chat memory components (such as ChatMemoryAdvisor, ChatMemory, or similar chat memory APIs).
    Affected if Your application uses Spring AI's chat memory functionality
  3. Inspect chat memory configuration
    Examine your Spring AI configuration files and code for chat memory setup. Look for how the memory store is configured (in-memory, database, vector store) and whether user/session identifiers are explicitly passed to memory operations.
    Affected if Chat memory is configured without explicit user-specific session isolation parameters, relying on default behavior
  4. Verify session context handling
    Review how chat memory operations are invoked: check if user ID or session ID parameters are consistently passed to store/retrieve operations, or if these parameters are omitted allowing the default shared context to be used.
    Affected if Code passes null, empty, or no user/session identifier to chat memory operations, using the default shared configuration

You are affected if your Spring AI version is 1.0.0-1.0.6 or 1.1.0-1.1.5, your application uses chat memory, and the memory context lacks explicit per-user isolation configuration.

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.7 / 1.1.6 or later
Fixed in 1.0.71.1.6
Interim mitigation

Review all Spring AI chat memory implementations and explicitly configure user-specific memory isolation settings. Ensure that each user session has its own dedicated memory context that cannot be accessed by other users.

Recommended fix Moderate confidence

Spring AI 1.0.7 or 1.1.6 (depending on your major version branch)

  1. 1. Identify your current Spring AI version by checking your project dependencies (e.g., pom.xml for Maven or build.gradle for Gradle)
  2. 2. For Spring AI 1.0.x users: upgrade to version 1.0.7 or later by updating the version in your dependency management
  3. 3. For Spring AI 1.1.x users: upgrade to version 1.1.6 or later by updating the version in your dependency management
  4. 4. After upgrading, review your chat memory configuration to ensure proper permissions are explicitly set according to your security requirements
  5. 5. Test the application to verify chat memory operates correctly with the updated version
Caveat Review the Spring AI release notes for 1.0.7 and 1.1.6 to check for any breaking changes relevant to your implementation

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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