Quick answers
- Is CVE-2026-47894 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47894 being exploited in the wild.
- How severe is CVE-2026-47894?
- Medium severity, with a CVSS score of 4.9, published 27 August 2026.
- Which products and versions are affected?
- Spring Cloud Config 3.1.14 and earlier, 4.0.0 through 4.2.8, 4.3.0 through 4.3.4, 5.0.0 through 5.0.4.
- Is there a fix for CVE-2026-47894?
- 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-47894 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-47894?
- Check whether you run 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 path traversal flaw in Spring Cloud Config Server's native environment repository handler that fails to properly validate and sanitize file paths. An attacker with network access to the Config Server can craft requests using path traversal sequences (such as `../`) to access configuration files beyond the configured repository boundary. No authentication is required if the server is network-accessible. This allows an attacker to read arbitrary configuration files on the system, exposing application secrets and sensitive infrastructure details. Patches are available in Spring Cloud Config 5.0.5, 4.3.5, and 4.2.9 or later.
Affected products
- Spring Cloud Config 3.1.14 and earlier, 4.0.0 through 4.2.8, 4.3.0 through 4.3.4, 5.0.0 through 5.0.4
Timeline
- 2026-08-27: disclosed