Spring Cloud Config Server Logged Sensitive Information

published 2026-05-07 6 mo ago modified 2026-10-26 13 d ago also GHSA-j6hh-h3cf-c2hf , EUVD-2026-28250

cvss: 4.4; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.2%; EPSS 0.2% chance of exploitation in 30 days, percentile 6%
public exploits: 0; none known

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.

Patch / fix

fixed in 2

maven org.springframework.cloud:spring-cloud-config-server 4.3.3, 5.0.3
Spring Spring Cloud Config 3.1.14, 4.1.10, 4.2.7, 4.3.3, 5.0.3

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-41004 updated 2026-11-05 cvss 4.4

Spring Cloud Config Server: Spring Cloud Config: Spring Cloud Config Server: Information disclosure via trace logging

Red Hat Enterprise Linux 8 log4j, log4j-jcl, log4j-web, log4j-slf4j Red Hat JBoss Enterprise Application Platform Expansion Pack spring-cloud-config-server
affected: workaround, no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 6 mo ago (2026-05-07)

Exploit prediction

0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	4.4	CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
GitHub	3.1	4.4	CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
maven	org.springframework.cloud:spring-cloud-config-server	>=3.1.0, <=3.1.13 >=4.1.0, <=4.1.9 >=4.2.0, <=4.2.6 >=4.3.0, <4.3.3 >=5.0.0, <5.0.3 >=3.0.0, <=3.0.7	4.3.3 5.0.3

Affected products

Spring Spring Cloud Config

Classification

Weakness

CWE-532 Insertion of Sensitive Information into Log File

Technology feeds

Spring rss critical rss

References

spring.io /security/cve-2026-41004
web, vendor-advisory
nvd.nist.gov /vuln/detail/CVE-2026-41004
advisory
github.com /spring-cloud/spring-cloud-config
package

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary