Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-41004: When enabling trace logging in Spring Cloud Config Server sensitive information was placed in plain text in th

17
Routine
MEDIUM 4.4UPGRADE

CVE-2026-41004 is a medium-severity flaw (CVSS 4.4) affecting spring cloud config. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

  • No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score4.4 (Medium)
Attack vectorLocal
Attack complexityLow
Privileges neededHigh
User interactionNone
EPSS exploit chance0.2% (top 94%)
CISA exploited listNo
WeaknessCWE-532
Published2026-05-07
Last modified2026-10-26
Publisher (CNA): VMware · Vendor: vmware

Share: LinkedIn · X · Reddit

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

vmware spring cloud config UPGRADE
Affected: >= 3.1.0 and < 3.1.14 · >= 4.1.0 and < 4.1.10 · >= 4.2.0 and < 4.2.7 · >= 4.3.0 and < 4.3.3 · >= 5.0.0 and < 5.0.3
Fixed in: 3.1.14, 4.1.10, 4.2.7, 4.3.3, 5.0.3
Safe to downgrade to: a release before 3.1.0
1. Check installed version
apt-cache policy spring-cloud-config || rpm -q spring-cloud-config || spring-cloud-config --version
2. UPGRADE to 3.1.14 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade spring-cloud-config
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade spring-cloud-config
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 3.1.0 (Debian / Ubuntu)
apt-cache madison spring-cloud-config sudo apt install spring-cloud-config=<VERSION_BEFORE_3.1.0> sudo apt-mark hold spring-cloud-config
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list spring-cloud-config sudo dnf downgrade spring-cloud-config-<VERSION_BEFORE_3.1.0> sudo dnf versionlock add spring-cloud-config
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-41004?

spring cloud config: upgrade to 3.1.14, 4.1.10, 4.2.7, 4.3.3, 5.0.3. Exact commands for each OS are on this page.

Is CVE-2026-41004 being exploited?

CVE-2026-41004 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-41004 affect?

CVE-2026-41004 affects spring cloud config. Severity is medium (CVSS 4.4). 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 Suppor

How urgent is CVE-2026-41004?

Priority 17/100. No elevated risk signals yet.

Software pages

VMware vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.