cve.bz

CVE-2026-41712 vmware spring ai: Incorrect Default Permissions

7.5 highEPSS 0.3%Fix available

High (7.5) in vmware spring ai. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in org.springframework.ai:spring-ai-client-chat 1.0.7, 1.1.6, 2.0.0-M6.

On this page
Spring AI's chat memory component contained a problematic default that, when not explicitly overridden, could result in unintended data exposure between users.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 18th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-05-12. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-276 Incorrect Default Permissions
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

  • org.springframework.ai:spring-ai-client-chat (Maven): fixed in 1.0.7, 1.1.6, 2.0.0-M6
  • org.springframework.ai:spring-ai-model (Maven): fixed in 1.0.7, 1.1.6, 2.0.0-M6
  • org.springframework.ai:spring-ai-advisors-vector-store (Maven): fixed in 1.0.7, 1.1.6, 2.0.0-M6
  • Vendor advisory: https://spring.io/security/cve-2026-41712

Ask an AI about this CVE

Show the promptExplain CVE-2026-41712 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-41712?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-41712?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-41712 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-41712

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-41712](https://cve.bz/cve/badge/CVE-2026-41712.svg)](https://cve.bz/cve/CVE-2026-41712)

HTML:

<a href="https://cve.bz/cve/CVE-2026-41712"><img src="https://cve.bz/cve/badge/CVE-2026-41712.svg" alt="CVE-2026-41712"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
VMware Spring AIfrom 1.0.0 before 1.0.7
VMware Spring AIfrom 1.1.0 before 1.1.6

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-q62f-h9x2-gcqcMavenorg.springframework.ai:spring-ai-client-chat<1.0.71.0.7
GHSA-q62f-h9x2-gcqcMavenorg.springframework.ai:spring-ai-client-chat>=1.1.0-M1 <1.1.61.1.6
GHSA-q62f-h9x2-gcqcMavenorg.springframework.ai:spring-ai-client-chat>=2.0.0-M1 <2.0.0-M62.0.0-M6
GHSA-q62f-h9x2-gcqcMavenorg.springframework.ai:spring-ai-model<1.0.71.0.7
GHSA-q62f-h9x2-gcqcMavenorg.springframework.ai:spring-ai-model>=1.1.0-M1 <1.1.61.1.6
GHSA-q62f-h9x2-gcqcMavenorg.springframework.ai:spring-ai-model>=2.0.0-M1 <2.0.0-M62.0.0-M6
GHSA-q62f-h9x2-gcqcMavenorg.springframework.ai:spring-ai-advisors-vector-store<1.0.71.0.7
GHSA-q62f-h9x2-gcqcMavenorg.springframework.ai:spring-ai-advisors-vector-store>=1.1.0-M1 <1.1.61.1.6
GHSA-q62f-h9x2-gcqcMavenorg.springframework.ai:spring-ai-advisors-vector-store>=2.0.0-M1 <2.0.0-M62.0.0-M6

Attack patterns (CAPEC)

  • CAPEC-1 Accessing Functionality Not Properly Constrained by ACLs Likelihood: High · Severity: High
  • CAPEC-81 Web Server Logs Tampering Likelihood: Medium · Severity: High
  • CAPEC-127 Directory Indexing Likelihood: High · Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON