Cleartext Storage of Sensitive Information Affecting log4j:2/log4j-slf4j package, versions *


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.17% (7th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL8-LOG4J-17261284
  • published9 Jun 2026
  • disclosed7 May 2026

Introduced: 7 May 2026

CVE-2026-41004  (opens in a new tab)
CWE-312  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:8 log4j:2/log4j-slf4j.

NVD Description

Note: Versions mentioned in the description apply only to the upstream log4j:2/log4j-slf4j package and not the log4j:2/log4j-slf4j package as distributed by RHEL. See How to fix? for RHEL:8 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1