cve.bz

CVE-2026-40979 vmware spring ai: Insecure Temporary File

6.1 mediumEPSS 0.1%Fix available

Medium (6.1) in vmware spring ai. EPSS 0.1% estimated probability of exploitation activity in the next 30 days. Fixed in org.springframework.ai:spring-ai-transformers 1.0.6, 1.1.5.

On this page
In Spring AI, having access to a shared environment can expose the ONNX model used by the application. Affected versions: Spring AI: 1.0.0 - 1.0.5 (fixed in 1.0.6), 1.1.0 - 1.1.4 (fixed in 1.1.5)

Severity

CVSS 3.1

6.1 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N
EPSS
0.1% (unchanged from 0.1% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 1st 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: no · Technical impact: partial, assessed 2026-04-28. 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-377 Insecure Temporary File deprecated by MITRE
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-40979 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-40979?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-40979?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-40979 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-40979

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-40979](https://cve.bz/cve/badge/CVE-2026-40979.svg)](https://cve.bz/cve/CVE-2026-40979)

HTML:

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

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Spring AIfrom 1.0.0 before 1.0.6
Spring AIfrom 1.1.0 before 1.1.5

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-r5hp-3cgj-j6xvMavenorg.springframework.ai:spring-ai-transformers>=1.0.0 <1.0.61.0.6
GHSA-r5hp-3cgj-j6xvMavenorg.springframework.ai:spring-ai-transformers>=1.1.0 <1.1.51.1.5

Attack patterns (CAPEC)

  • CAPEC-149 Explore for Predictable Temporary File Names Severity: Medium
  • CAPEC-155 Screen Temporary Files for Sensitive Information Likelihood: Medium · Severity: Medium

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

References

Check your stackJSON