Skip to content

← Public intelligence

Maven package

org.springframework.ai:spring-ai-advisors-vector-store

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.5MavenPublished

    Spring AI: ChatMemory DEFAULT_CONVERSATION_ID causes unintended cross-user data leakage

    CVE-2026-41712 · GHSA-q62f-h9x2-gcqc

    Affected
    • Maven org.springframework.ai:spring-ai-advisors-vector-store < 1.0.7; >= 1.1.0-M1, < 1.1.6; >= 2.0.0-M1, < 2.0.0-M6
    Fixed in
    2.0.0-M61.1.61.0.7· Vendor fix available
    Issue
    Spring AI's chat memory component contained a problematic default that, when not explicitly overridden, could result in unintended data exposure between users.

    Recommended action: Upgrade to 2.0.0-M6 (pre-release), 1.1.6 or 1.0.7 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Medium, CVSS 5.9MavenPublished

    Spring AI's VectorStoreChatMemoryAdvisor conversation scoping can lead to cross-tenant memory exfiltration

    CVE-2026-40966 · GHSA-v6x6-pjxw-3pv2

    Affected
    • Maven org.springframework.ai:spring-ai-advisors-vector-store >= 1.0.0, < 1.0.6; >= 1.1.0, < 1.1.5
    Fixed in
    1.1.51.0.6· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 1.1.5 or 1.0.6 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →