Spring Cloud Config Server Susceptible To TOCTOU Attack When Using SVN

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

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

The base directory (spring.cloud.config.server.svn.basedir) used by the Spring Cloud Config Server to clone SVN repositories to is susceptible to time-of-check-time-of-use (TOCTOU) attacks. 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

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-47836 updated 2026-09-21 cvss 7.2

org.springframework.cloud/spring-cloud-config-server: Spring Cloud Config Server: TOCTOU vulnerability in SVN base directory

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: total
Assessed: 2 mo ago (2026-08-26)

Exploit prediction

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

CVSS scores

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

Affected products

Spring Spring Cloud Config

Classification

Weakness

CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition

Technology feeds

Spring rss critical rss

References

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

Sources

CVE List CVE-2026-47836
NVD CVE-2026-47836

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