CVE-2026-41004

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.

Published: 2026-05-07 Last update: 2026-05-12 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-41004 is rated Low Risk (17.7/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.01%). Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-41004

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-07 — 0.01% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-41004

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.4 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 0.8 3.6 [email protected]

Weakness enumeration for CVE-2026-41004

GitHub Security Advisory for CVE-2026-41004

GHSA-j6hh-h3cf-c2hf · Severity: medium · Ecosystem: maven — Spring Cloud Config Server Logged Sensitive Information

Affected software / configurations for CVE-2026-41004

Vendor Product Version Raw CPE
vmware spring_cloud_config >= 3.1.0, < 3.1.14 cpe:2.3:a:vmware:spring_cloud_config:*:*:*:*:*:*:*:*
vmware spring_cloud_config >= 4.1.0, < 4.1.10 cpe:2.3:a:vmware:spring_cloud_config:*:*:*:*:*:*:*:*
vmware spring_cloud_config >= 4.2.0, < 4.2.7 cpe:2.3:a:vmware:spring_cloud_config:*:*:*:*:*:*:*:*
vmware spring_cloud_config >= 4.3.0, < 4.3.3 cpe:2.3:a:vmware:spring_cloud_config:*:*:*:*:*:*:*:*
vmware spring_cloud_config >= 5.0.0, < 5.0.3 cpe:2.3:a:vmware:spring_cloud_config:*:*:*:*:*:*:*:*

References for CVE-2026-41004

cvelogic Threat Intelligence