Expression Language Injection The advisory has been revoked - it doesn't affect any version of package log4j-core.src  (opens in a new tab)


Threat Intelligence

Exploit Maturity
Attacked
EPSS
94.34% (100th 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-RHEL10-LOG4JCORESRC-15340297
  • published25 Feb 2026
  • disclosed14 Dec 2021

Introduced: 14 Dec 2021

CVE-2021-45046  (opens in a new tab)
CWE-917  (opens in a new tab)

Amendment

The Red Hat security team deemed this advisory irrelevant for RHEL:10.

NVD Description

Note: Versions mentioned in the description apply only to the upstream log4j-core.src package and not the log4j-core.src package as distributed by RHEL.

It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allows attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in an information leak and remote code execution in some environments and local code execution in all environments. Log4j 2.16.0 (Java 8) and 2.12.2 (Java 7) fix this issue by removing support for message lookup patterns and disabling JNDI functionality by default.

References