# CVE-2026-47837: Spring Cloud Config Server Monitor Endpoint Does Not Validate Webhook Requests

> Attackers can access the Spring Cloud Config Server monitor endpoint without authentication, bypassing security controls.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** GHSA-9w38-hp46-g6xj

## What is CVE-2026-47837?

CVE-2026-47837 is a medium-severity missing authorization vulnerability in Spring Cloud Config, published on 26 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Missing Authentication for Critical Function vulnerability in Spring Spring Cloud Config allows Webhook requests to Spring Cloud Config Server's /monitor endpoint are not validated.

This issue affects Spring Cloud Config: from 5.0.0 through 5.0.4, from 4.3.0 through 4.3.4, from 4.0.0 through 4.2.8, and through 3.1.14.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 1 product.


Products: Vmware Spring Cloud Config.

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

Upgrade to a fixed version.

## Is CVE-2026-47837 being exploited?

There is no known exploitation of CVE-2026-47837 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-47837 and fix it if it is affected.

What it is: CVE-2026-47837 is a medium-severity missing authorization vulnerability in Spring Cloud Config, published on 26 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-47837 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-47837/ (Markdown: https://insights.sbomify.com/CVE-2026-47837/index.md)
```

## Sources

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

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