Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-q62f-h9x2-gcqc

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

CVSS 7.5 HighEPSS 0.0026 · 17th percentile

Published by the GitHub Advisory Database at 12 May 2026, 12:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.springframework.ai:spring-ai-client-chatMaven<1.0.7 || >=1.1.0-M1, <1.1.6 || >=2.0.0-M1, <2.0.0-M61.0.7, 1.1.6, 2.0.0-M6
org.springframework.ai:spring-ai-modelMaven<1.0.7 || >=1.1.0-M1, <1.1.6 || >=2.0.0-M1, <2.0.0-M61.0.7, 1.1.6, 2.0.0-M6
org.springframework.ai:spring-ai-advisors-vector-storeMaven<1.0.7 || >=1.1.0-M1, <1.1.6 || >=2.0.0-M1, <2.0.0-M61.0.7, 1.1.6, 2.0.0-M6
Identifiers
GHSA-q62f-h9x2-gcqc · CVE-2026-41712
Weakness (CWE)
CWE-276
Tags
Published
12 May 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Spring AI's chat memory components, in the spring-ai-client-chat, spring-ai-model and spring-ai-advisors-vector-store packages, are affected in versions before 1.0.7, from 1.1.0-M1 before 1.1.6, and from 2.0.0-M1 before 2.0.0-M6. When the default conversation ID is not explicitly overridden, conversation data can be exposed between users. The source gives few details about the attack requirements. Upgrade to 1.0.7, 1.1.6, or 2.0.0-M6, depending on your release line, and set an explicit conversation ID per user until then.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N CNA (vmware)
  • CISA KEV Not listed.
  • EPSS 0.0026, the 17th percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:16 UTC First seen by agentprime
  2. 31 Oct 2026, 14:16 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.