Spring Cloud Config Server Monitor Endpoint Does Not Validate Webhook Requests

published 2026-08-26 2 mo ago modified 2026-09-04 2 mo ago also EUVD-2026-66638

cvss: 6.8; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.6%; EPSS 0.6% chance of exploitation in 30 days, percentile 46%
public exploits: 0; none known

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.

Patch / fix

fixed in 1

vmware spring_cloud_config 3.1.15, 4.2.9, 4.3.5, 5.0.5

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-47837 updated 2026-09-09 cvss 6.8

org.springframework.cloud/spring-cloud-config-server: Spring Cloud Config Server: Denial of Service via unauthenticated monitor endpoint

Red Hat All currently supported Red Hat products
not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 2 mo ago (2026-08-26)

Exploit prediction

0.55% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	6.8	CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H
NVD	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Spring Spring Cloud Config

Classification

Weakness

CWE-306 Missing Authentication for Critical Functionality

Technology feeds

Spring rss critical rss

References

spring.io /security/cve-2026-47837
vendor-advisory

Sources

CVE List CVE-2026-47837
NVD CVE-2026-47837

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary