Spring Cloud Config Server Susceptible To TOCTOU AttackGHSA-86wq-234q-r6wg
HIGHGHSA-86wq-234q-r6wg is a high-severity (CVSS 7.2) CWE-367 vulnerability in org.springframework.cloud:spring-cloud-config-server. A fix is available for org.springframework.cloud:spring-cloud-config-server — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-86wq-234q-r6wg.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.springframework.cloud:spring-cloud-config-server☕org.springframework.cloud:spring-cloud-config-server☕org.springframework.cloud:spring-cloud-config-server☕org.springframework.cloud:spring-cloud-config-server☕org.springframework.cloud:spring-cloud-config-server☕org.springframework.cloud:spring-cloud-config-serverReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
The base directory (spring.cloud.config.server.git.basedir) used by the Spring Cloud Config Server to clone Git repositories to is susceptible to time-of-check-time-of-use (TOCTOU) attacks.
- Spring Cloud Config 3.0.x: affected from 3.0.0 through 3.0.7 (inclusive); no open-source upgrade available.
- Spring Cloud Config 3.1.x: affected from 3.1.0 through 3.1.13 (inclusive); no open-source upgrade available.
- Spring Cloud Config 4.1.x: affected from 4.1.0 through 4.1.9 (inclusive); no open-source upgrade available.
- Spring Cloud Config 4.2.x: affected from 4.2.0 through 4.2.6 (inclusive); no open-source upgrade available.
- Spring Cloud Config 4.3.x: affected from 4.3.0 through 4.3.2 (inclusive); upgrade to 4.3.3 or greater.
- Spring Cloud Config 5.0.x: affected from 5.0.0 through 5.0.2 (inclusive); upgrade to 5.0.3 or greater.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.cloud:spring-cloud-config-server | ≥ 3.1.0 | No fix |
| ☕Maven | org.springframework.cloud:spring-cloud-config-server | ≥ 4.1.0 | No fix |
| ☕Maven | org.springframework.cloud:spring-cloud-config-server | ≥ 4.2.0 | No fix |
| ☕Maven | org.springframework.cloud:spring-cloud-config-server | ≥ 4.3.0&&< 4.3.3 | 4.3.3org.springframework.cloud:spring-cloud-config-server:4.3.3 |
| ☕Maven | org.springframework.cloud:spring-cloud-config-server | ≥ 5.0.0&&< 5.0.3 | 5.0.3org.springframework.cloud:spring-cloud-config-server:5.0.3 |
| ☕Maven | org.springframework.cloud:spring-cloud-config-server | ≥ 3.0.0 | No fix |
Affected Products
spring cloud configvmwareDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.cloud:spring-cloud-config-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
A fix is available for GHSA-86wq-234q-r6wg; check the affected-versions list above or the advisory for the patched release of org.springframework.cloud:spring-cloud-config-server, then make sure no transitive dependency still pins the vulnerable range.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is GHSA-86wq-234q-r6wg in your dependencies?
Find it across Maven, including transitive dependencies.