Loading vulnerability…
CVE-2026-41004 is a medium-severity information disclosure vulnerability in Spring Cloud Config Server. When trace logging is enabled, the server writes sensitive information in plain text to its logs. The issue affects the product’s internal logging behavior rather than a memory corruption or code execution path, and can result in credentials, configuration secrets, or other confidential values being recorded in log files or forwarded to centralized logging systems. Affected versions are Spring Cloud Config 3.1.0 through 3.1.13, 4.1.0 through 4.1.9, 4.2.0 through 4.2.6, 4.3.0 through 4.3.2, and 5.0.0 through 5.0.2.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A medium-severity information exposure vulnerability in Spring Cloud Config Server where trace logging can write sensitive information in plaintext to log files.
A medium-severity vulnerability involving plaintext sensitive data in trace logs in the Spring Cloud Config ecosystem, mentioned as part of the same coordinated disclosure batch.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.