# CVE-2026-59315: Spring Cloud Config Monitor Denial of Service

> Attackers can cause denial of service in Spring Cloud Config Monitor by sending malicious payloads, affecting service availability.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-m8cp-w83w-vr3r

## What is CVE-2026-59315?

CVE-2026-59315 is a medium-severity denial of service vulnerability in Spring Cloud Config, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2026-59315?

It affects 1 product.


Products: Vmware Spring Cloud Config.

## How do I fix CVE-2026-59315?

No fix has been published for CVE-2026-59315 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-59315 being exploited?

There is no known exploitation of CVE-2026-59315 in the wild and no public exploit code.

## Other vulnerabilities in Spring Cloud Config

- [CVE-2020-5410](https://insights.sbomify.com/CVE-2020-5410/): VMware Tanzu Spring Cloud Config Directory Traversal (high 7.5, exploited in the wild)
- [CVE-2026-40982](https://insights.sbomify.com/CVE-2026-40982/): Spring Cloud Config vulnerable to Path Traversal (critical 9.1)
- [CVE-2026-22739](https://insights.sbomify.com/CVE-2026-22739/): Spring Cloud Config Profile Substitution Can Allow Unintended Access To Files And Enable SSRF Attacks (high 8.6)
- [CVE-2026-40981](https://insights.sbomify.com/CVE-2026-40981/): Spring Cloud Config has an Authorization Bypass Through User-Controlled Key (high 7.5)
- [CVE-2026-41002](https://insights.sbomify.com/CVE-2026-41002/): Spring Cloud Config Server Susceptible To TOCTOU Attack (high 7.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-59315 and fix it if it is affected.

What it is: CVE-2026-59315 is a medium-severity denial of service vulnerability in Spring Cloud Config, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-59315 in the wild and no public exploit code.

Affected product: Spring Cloud Config. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-59315/ (Markdown: https://insights.sbomify.com/CVE-2026-59315/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-59315
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-59315
- OSV: https://osv.dev/vulnerability/CVE-2026-59315

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-59315/
Summaries are generated and may contain mistakes; the official description above is the record.