CVE-2026-41004: Medium severity VMware Spring Cloud Config vulnerability
When enabling trace logging in Spring Cloud Config Server sensitive information was placed in plain text in the logs. Spring Cloud Config 3.1.x: affected from 3.1.0 through 3.1.13 (inclusive); upgrade to 3.1.14 or greater (Enterprise Support Only). Spring Cloud Config 4.1.x: affected from 4.1.0 through 4.1.9 (inclusive); upgrade to 4.1.10 or greater (Enterprise Support Only). Spring Cloud Config 4.2.x: affected from 4.2.0 through 4.2.6 (inclusive); upgrade to 4.2.7 or greater (Enterprise Support Only). 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 Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-41004?
CVE-2026-41004 is considered a high severity vulnerability due to the exposure of sensitive information in trace logs.
How do I fix CVE-2026-41004?
To fix CVE-2026-41004, upgrade Spring Cloud Config to version 3.1.14 or greater, or to version 4.1.10 or greater.
What versions of Spring Cloud Config are affected by CVE-2026-41004?
CVE-2026-41004 affects Spring Cloud Config versions from 3.1.0 through 3.1.13, and from 4.1.0 through 4.1.9 among others.
What type of data was exposed in CVE-2026-41004?
CVE-2026-41004 exposed sensitive information in plain text in the trace logs, which could potentially be accessed by unauthorized users.
Is CVE-2026-41004 related to all Spring Cloud Config versions?
No, CVE-2026-41004 specifically affects certain versions of Spring Cloud Config, not all releases.