CVE-2026-59299 Vulnerability Analysis & Exploit Details

CVE-2026-59299
Vulnerability Scoring

3.1
/10
Moderate Risk

Exploiting CVE-2026-59299 requires specific conditions, leading to a moderate security impact.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: High
    High-level privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: Required
    User interaction is necessary for successful exploitation.

CVE-2026-59299 Details

Status: Analyzed

Last updated: 🕧 02 Sep 2026, 00:44 UTC
Originally published on: 🕗 27 Aug 2026, 20:17 UTC

Time between publication and last update: 5 days

CVSS Release: version 3

CVSS3 Source

security@vmware.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2026-59299 Vulnerability Summary

CVE-2026-59299: Composition lookup can potentially poison base function in Spring Cloud Function. Spring Cloud Function 5.0.0 - 5.0.3 Spring Cloud Function 4.3.0 - 4.3.4 Spring Cloud Function 4.2.0 - 4.2.7 Spring Cloud Function 3.2.16 and earlier

Assessing the Risk of CVE-2026-59299

Access Complexity Graph

The exploitability of CVE-2026-59299 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-59299

The exploitability of CVE-2026-59299 is influenced by multiple factors. Security teams should analyze system configurations and apply appropriate countermeasures to mitigate threats.

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-59299, 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-59299, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: Low
    CVE-2026-59299 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: Low
    Exploiting CVE-2026-59299 may cause minor changes to data without severely impacting its accuracy.
  • Availability: None
    CVE-2026-59299 does not impact system availability.

CVE-2026-59299 References

External References

CWE Common Weakness Enumeration

CWE-471

CAPEC Common Attack Pattern Enumeration and Classification

  • Application API Message Manipulation via Man-in-the-Middle CAPEC-384 An attacker manipulates either egress or ingress data from a client within an application framework in order to change the content of messages. Performing this attack can allow the attacker to gain unauthorized privileges within the application, or conduct attacks such as phishing, deceptive strategies to spread malware, or traditional web-application attacks. The techniques require use of specialized software that allow the attacker to perform adversary-in-the-middle (CAPEC-94) communications between the web browser and the remote system. Despite the use of AiTH software, the attack is actually directed at the server, as the client is one node in a series of content brokers that pass information along to the application framework. Additionally, it is not true "Adversary-in-the-Middle" attack at the network layer, but an application-layer attack the root cause of which is the master applications trust in the integrity of code supplied by the client.
  • Transaction or Event Tampering via Application API Manipulation CAPEC-385 An attacker hosts or joins an event or transaction within an application framework in order to change the content of messages or items that are being exchanged. Performing this attack allows the attacker to manipulate content in such a way as to produce messages or content that look authentic but may contain deceptive links, substitute one item or another, spoof an existing item and conduct a false exchange, or otherwise change the amounts or identity of what is being exchanged. The techniques require use of specialized software that allow the attacker to man-in-the-middle communications between the web browser and the remote system in order to change the content of various application elements. Often, items exchanged in game can be monetized via sales for coin, virtual dollars, etc. The purpose of the attack is for the attack to scam the victim by trapping the data packets involved the exchange and altering the integrity of the transfer process.
  • Application API Navigation Remapping CAPEC-386 An attacker manipulates either egress or ingress data from a client within an application framework in order to change the destination and/or content of links/buttons displayed to a user within API messages. Performing this attack allows the attacker to manipulate content in such a way as to produce messages or content that looks authentic but contains links/buttons that point to an attacker controlled destination. Some applications make navigation remapping more difficult to detect because the actual HREF values of images, profile elements, and links/buttons are masked. One example would be to place an image in a user's photo gallery that when clicked upon redirected the user to an off-site location. Also, traditional web vulnerabilities (such as CSRF) can be constructed with remapped buttons or links. In some cases navigation remapping can be used for Phishing attacks or even means to artificially boost the page view, user site reputation, or click-fraud.
  • Navigation Remapping To Propagate Malicious Content CAPEC-387 An adversary manipulates either egress or ingress data from a client within an application framework in order to change the content of messages and thereby circumvent the expected application logic.
  • Application API Button Hijacking CAPEC-388 An attacker manipulates either egress or ingress data from a client within an application framework in order to change the destination and/or content of buttons displayed to a user within API messages. Performing this attack allows the attacker to manipulate content in such a way as to produce messages or content that looks authentic but contains buttons that point to an attacker controlled destination.

Vulnerable Configurations

  • cpe:2.3:a:vmware:spring_cloud_function:3.2.0:-:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:3.2.0:-:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:3.2.0:m1:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:3.2.0:m1:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:3.2.0:m2:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:3.2.0:m2:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:3.2.0:m3:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:3.2.0:m3:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:3.2.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:3.2.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:3.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:3.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:3.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:3.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:3.2.3:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:3.2.3:*:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:3.2.4:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:3.2.4:*:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:3.2.5:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:3.2.5:*:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:3.2.6:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:3.2.6:*:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:3.2.16:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:3.2.16:*:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:4.2.0:-:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:4.2.0:-:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:4.2.0:m1:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:4.2.0:m1:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:4.2.0:m2:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:4.2.0:m2:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:4.2.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:4.2.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:4.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:4.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:4.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:4.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:4.2.3:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:4.2.3:*:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:4.2.4:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:4.2.4:*:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:4.2.6:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:4.2.6:*:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:4.3.0:-:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:4.3.0:-:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:4.3.0:m1:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:4.3.0:m1:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:4.3.0:m2:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:4.3.0:m2:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:4.3.0:m3:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:4.3.0:m3:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:4.3.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:4.3.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:4.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:4.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:4.3.2:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:4.3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:4.3.3:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:4.3.3:*:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:5.0.0:-:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:5.0.0:-:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:5.0.0:m1:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:5.0.0:m1:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:5.0.0:m2:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:5.0.0:m2:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:5.0.0:m3:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:5.0.0:m3:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:5.0.0:m4:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:5.0.0:m4:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:5.0.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:5.0.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:5.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:5.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:vmware:spring_cloud_function:5.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:vmware:spring_cloud_function:5.0.2:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-59299: 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...