VMware Spring Cloud Config up to 3.1.14/4.2.8/4.3.4/5.0.4 Monitor resource consumption

Summaryinfo

A vulnerability identified as problematic has been detected in VMware Spring Cloud Config up to 3.1.14/4.2.8/4.3.4/5.0.4. This vulnerability affects unknown code of the component Monitor. The manipulation leads to resource consumption. This vulnerability is uniquely identified as CVE-2026-59315. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in VMware Spring Cloud Config up to 3.1.14/4.2.8/4.3.4/5.0.4. It has been rated as problematic. This issue affects some unknown functionality of the component Monitor. The manipulation with an unknown input leads to a resource consumption vulnerability. Using CWE to declare the problem leads to CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. Impacted is availability. The summary by CVE is:

The Spring Cloud Config Monitor is susceptible to Denial of Service attacks via malicious payloads. Spring Cloud Config 5.0.0 - 5.0.4 Spring Cloud Config 4.3.0 - 4.3.4 Spring Cloud Config 4.0.0 - 4.2.8 Spring Cloud Config 3.1.14 and earlier

The advisory is shared at spring.io. The identification of this vulnerability is CVE-2026-59315 since 07/04/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/27/2026). MITRE ATT&CK project uses the attack technique T1499 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Cloud Software

Vendor

• VMware

Name

• Spring Cloud Config

Version

• 3.1.0
• 3.1.1
• 3.1.2
• 3.1.3
• 3.1.4
• 3.1.5
• 3.1.6
• 3.1.7
• 3.1.8
• 3.1.9
• 3.1.10
• 3.1.11
• 3.1.12
• 3.1.13
• 3.1.14
• 4.2.0
• 4.2.1
• 4.2.2
• 4.2.3
• 4.2.4
• 4.2.5
• 4.2.6
• 4.2.7
• 4.2.8
• 4.3.0
• 4.3.1
• 4.3.2
• 4.3.3
• 4.3.4
• 5.0.0
• 5.0.1
• 5.0.2
• 5.0.3
• 5.0.4

License

• commercial

Website

• Vendor: https://www.vmware.com/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion