Quick answers
- Is CVE-2026-47836 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47836 being exploited in the wild.
- How severe is CVE-2026-47836?
- High severity, with a CVSS score of 7.2, published 26 August 2026.
- Which products and versions are affected?
- VMware Spring Cloud Config 3.1.14 and earlier, 4.0.0–4.2.8, 4.3.0–4.3.4, 5.0.0–5.0.4.
- Is there a fix for CVE-2026-47836?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-47836 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-47836?
- Check whether you run VMware Spring Cloud Config at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a time-of-check-time-of-use (TOCTOU) race condition in the spring.cloud.config.server.svn.basedir parameter used when cloning SVN repositories. An attacker with network access to the Spring Cloud Config Server can exploit the window between directory validation and actual file operations to perform directory substitution or symlink attacks. This allows arbitrary file write or read access with the privileges of the Config Server process. The vulnerability affects Spring Cloud Config versions 3.1.14 and earlier, 4.0.0 through 4.2.8, 4.3.0 through 4.3.4, and 5.0.0 through 5.0.4. Patches are available for affected versions.
Affected products
- VMware Spring Cloud Config 3.1.14 and earlier, 4.0.0–4.2.8, 4.3.0–4.3.4, 5.0.0–5.0.4
Timeline
- 2026-08-26: disclosed