CVE-2026-47852 Vulnerability Analysis & Exploit Details

CVE-2026-47852
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2026-47852 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-47852 Details

Status: Analyzed

Last updated: 🕗 04 Sep 2026, 20:08 UTC
Originally published on: 🕐 27 Aug 2026, 01:17 UTC

Time between publication and last update: 8 days

CVSS Release: version 3

CVSS3 Source

security@vmware.com

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

CVE-2026-47852 Vulnerability Summary

CVE-2026-47852: A local attacker on a multi-user host can pre-create the deterministic cache path and plant a malicious ONNX model file. Spring AI 2.0.0 Spring AI 1.1.0 - 1.1.8 Spring AI 1.0.0 - 1.0.9

Assessing the Risk of CVE-2026-47852

Access Complexity Graph

The exploitability of CVE-2026-47852 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-47852

With low attack complexity and no required privileges, CVE-2026-47852 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-47852, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-47852, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2026-47852 has no significant impact on data confidentiality.
  • Integrity: High
    CVE-2026-47852 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: None
    CVE-2026-47852 does not impact system availability.

CVE-2026-47852 References

External References

CWE Common Weakness Enumeration

CWE-377

CAPEC Common Attack Pattern Enumeration and Classification

  • Explore for Predictable Temporary File Names CAPEC-149 An attacker explores a target to identify the names and locations of predictable temporary files for the purpose of launching further attacks against the target. This involves analyzing naming conventions and storage locations of the temporary files created by a target application. If an attacker can predict the names of temporary files they can use this information to mount other attacks, such as information gathering and symlink attacks.
  • Screen Temporary Files for Sensitive Information CAPEC-155 An adversary exploits the temporary, insecure storage of information by monitoring the content of files used to store temp data during an application's routine execution flow. Many applications use temporary files to accelerate processing or to provide records of state across multiple executions of the application. Sometimes, however, these temporary files may end up storing sensitive information. By screening an application's temporary files, an adversary might be able to discover such sensitive information. For example, web browsers often cache content to accelerate subsequent lookups. If the content contains sensitive information then the adversary could recover this from the web cache.

Vulnerable Configurations

  • cpe:2.3:a:vmware:spring_ai:1.0.0:-:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_ai:1.0.0:-:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_ai:1.0.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_ai:1.0.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_ai:1.0.0:milestone1:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_ai:1.0.0:milestone1:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_ai:1.0.0:milestone2:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_ai:1.0.0:milestone2:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_ai:1.0.0:milestone3:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_ai:1.0.0:milestone3:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_ai:1.0.0:milestone4:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_ai:1.0.0:milestone4:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_ai:1.0.0:milestone5:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_ai:1.0.0:milestone5:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_ai:1.0.0:milestone6:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_ai:1.0.0:milestone6:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_ai:1.0.0:milestone7:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_ai:1.0.0:milestone7:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_ai:1.0.0:milestone8:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_ai:1.0.0:milestone8:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_ai:1.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_ai:1.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_ai:1.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_ai:1.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_ai:1.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_ai:1.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_ai:1.0.4:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_ai:1.0.4:*:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_ai:1.0.5:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_ai:1.0.5:*:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_ai:1.0.6:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_ai:1.0.6:*:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_ai:1.0.7:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_ai:1.0.7:*:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_ai:1.0.9:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_ai:1.0.9:*:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_ai:1.1.0:-:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_ai:1.1.0:-:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_ai:1.1.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_ai:1.1.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_ai:1.1.0:milestone1:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_ai:1.1.0:milestone1:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_ai:1.1.0:milestone2:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_ai:1.1.0:milestone2:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_ai:1.1.0:milestone3:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_ai:1.1.0:milestone3:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_ai:1.1.0:milestone4:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_ai:1.1.0:milestone4:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_ai:1.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_ai:1.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_ai:1.1.2:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_ai:1.1.2:*:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_ai:1.1.3:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_ai:1.1.3:*:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_ai:1.1.4:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_ai:1.1.4:*:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_ai:1.1.5:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_ai:1.1.5:*:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_ai:1.1.6:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_ai:1.1.6:*:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_ai:1.1.7:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_ai:1.1.7:*:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_ai:1.1.8:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_ai:1.1.8:*:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_ai:2.0.0:-:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_ai:2.0.0:-:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-47852: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-97663 – The Customer Reviews for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Author Name in all versions up t...
  • CVE-2026-97641 – The Relevanssi – A Better Search plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content in all versions up to, and i...
  • CVE-2026-97637 – The JSON API Auth plugin for WordPress is vulnerable to Authentication Bypass via Cached Session Cookie Disclosure in all versions up to, and inclu...
  • CVE-2026-97634 – The Event Tickets and Registration plugin for WordPress is vulnerable to generic SQL Injection via the 'orderby' parameter in all versions up to, a...
  • CVE-2026-97342 – The JetFormBuilder — Dynamic Blocks Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'choice' Post Meta via Inser...