vulntracker.iovulntracker.io
© 2026 vulntracker.io

CVE-2026-41004

MEDIUM
4.4
CVSS Score
Published: May 7, 2026 at 03:51 AM UTC
Updated: June 17, 2026 at 10:46 AM UTC
2 products affected across 2 vendorsSpring Cloud ConfigSpring Cloud Config

Using Spring Cloud Config by Spring?

Get instant alerts when new vulnerabilities affect Spring Cloud Config - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Start FreeSign In
Severity
MEDIUM4.4
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Spring Cloud Config· VMware
95%
3.1.0 ≤ v < 3.1.144.1.0 ≤ v < 4.1.104.2.0 ≤ v < 4.2.74.3.0 ≤ v < 4.3.35.0.0 ≤ v < 5.0.3
Spring Cloud Config· Spring
60%
3.1.0 ≤ v < 3.1.144.1.0 ≤ v < 4.1.104.2.0 ≤ v < 4.2.74.3.0 ≤ v < 4.3.35.0.0 ≤ v < 5.0.33.1.04.1.04.2.04.3.05.0.0
Affected range stops below 3.1.14, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.1.10, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.2.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.3.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.0.3, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (1)

Vendor Advisory
Source: cverecord
https://spring.io/security/cve-2026-41004

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

4.4MEDIUMvmware
Attack Vector
LOCAL
Complexity
LOW
Privileges
HIGH
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-532

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create accountSign in
Free plan, no card