# Spring AI: ChatMemory DEFAULT_CONVERSATION_ID causes unintended cross-user data leakage Advisory record · `GHSA-q62f-h9x2-gcqc` - **Identifiers:** `GHSA-q62f-h9x2-gcqc` · `CVE-2026-41712` - **State:** Confirmed - **Severity:** CVSS 7.5 High - **Critical:** No - **Weakness (CWE):** [CWE-276](https://cwe.mitre.org/data/definitions/276.html) - **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md) - **Published:** 12 May 2026 - **Updated:** 10 Sept 2026 - **Reviewed by a person:** No 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. ## Affected packages - `org.springframework.ai:spring-ai-client-chat` (Maven): affected `<1.0.7 || >=1.1.0-M1, <1.1.6 || >=2.0.0-M1, <2.0.0-M6`; fixed in `1.0.7`, `1.1.6`, `2.0.0-M6` - `org.springframework.ai:spring-ai-model` (Maven): affected `<1.0.7 || >=1.1.0-M1, <1.1.6 || >=2.0.0-M1, <2.0.0-M6`; fixed in `1.0.7`, `1.1.6`, `2.0.0-M6` - `org.springframework.ai:spring-ai-advisors-vector-store` (Maven): affected `<1.0.7 || >=1.1.0-M1, <1.1.6 || >=2.0.0-M1, <2.0.0-M6`; fixed in `1.0.7`, `1.1.6`, `2.0.0-M6` ## 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 - 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`, from 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 - 31 Oct 2026, 14:16 UTC: First seen by agentprime - 31 Oct 2026, 14:16 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-q62f-h9x2-gcqc) ## Sources - [GitHub Advisory Database: GHSA-q62f-h9x2-gcqc](https://github.com/advisories/GHSA-q62f-h9x2-gcqc) - [OSV: GHSA-q62f-h9x2-gcqc](https://osv.dev/vulnerability/GHSA-q62f-h9x2-gcqc) - - - 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. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .