How severe is CVE-2026-47894?

CVE-2026-47894 has a CVSS 3.x base score of 4.9, rated medium severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2026-47894 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (40th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-47894?

CVE-2026-47894 affects Vmware Spring Cloud Config. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-47894?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2026-47894 published?

CVE-2026-47894 was published on 2026-08-27 and last updated on 2026-09-01.

CVE-2026-47894

CVE-2026-47894 is a medium-severity vulnerability in Vmware Spring Cloud Config with a CVSS 3.x base score of 4.9. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 3.x base score 4.9)
EPSS exploit prediction: 0% (40th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Vmware Spring Cloud Config
Published: 2026-08-27
Last modified: 2026-09-01

Description

Spring Cloud Config Server native environment repository allows exposure of configuration files outside of the configured repository path. 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

Frequently asked questions

What is CVE-2026-47894?: Spring Cloud Config Server native environment repository allows exposure of configuration files outside of the configured repository path. 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
How severe is CVE-2026-47894?: CVE-2026-47894 has a CVSS 3.x base score of 4.9, rated medium severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2026-47894 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (40th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-47894?: CVE-2026-47894 affects Vmware Spring Cloud Config. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-47894?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2026-47894 published?: CVE-2026-47894 was published on 2026-08-27 and last updated on 2026-09-01.

References

https://spring.io/security/cve-2026-47894

Affected products (1)

cpe:2.3:a:vmware:spring_cloud_config:*:*:*:*:*:*:*:*

More vulnerabilities in Vmware Spring Cloud Config

CVE-2026-40982 — Critical (CVSS 9.1): Spring Cloud Config allows applications to serve arbitrary text and binary files through the spring-cloud-config-server…
CVE-2026-22739 — High (CVSS 8.6): Vulnerability in Spring Cloud when substituting the profile parameter from a request made to the Spring Cloud Config…
CVE-2026-40981 — High (CVSS 7.5): When using Google Secrets Manager as a backend for the Spring Cloud Config server a client can craft a request to the…
CVE-2020-5410 — High (CVSS 7.5): Spring Cloud Config, versions 2.2.x prior to 2.2.3, versions 2.1.x prior to 2.1.9, and older unsupported versions allow…
CVE-2026-47836 — High (CVSS 7.2): The base directory (spring.cloud.config.server.svn.basedir) used by the Spring Cloud Config Server to clone SVN…
CVE-2026-41002 — High (CVSS 7.2): The base directory (`spring.cloud.config.server.git.basedir`) used by the Spring Cloud Config Server to clone Git…

All CVEs affecting Vmware Spring Cloud Config →