maven package report

Is org.apache.logging.log4j:log4j-core safe?

11 known vulnerabilities, worst severity CRITICAL.

cvss
9.0

how bad it is if exploited, out of 10

epss
100.0%

chance of exploitation in the next 30 days

xyz score
7.3

CyberXYZ composite, out of 10

fig. 01 — GHSA-7rjr-3q55-vv33, the advisory selected below

// advisories

GHSA-7rjr-3q55-vv33

CRITICALCVE-2021-45046

The fix to address [CVE-2021-44228](https://nvd.nist.gov/vuln/detail/CVE-2021-44228) in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allow 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

Affected
>= 2.13.0, < 2.16.0
Fixed in
2.16.0
Weakness
CWE-502
Published
2021-12-14
Source
github

GHSANVDMITREreferencereferencereferencereferencereferencereferencereferencereferencereference

// dependencies

0 direct

Sign in for dependency paths and remediation

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so maven packages are not covered.

Checked 2026-09-22 at 02:56 UTC. The most recent advisory here was published 2026-04-10. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is org.apache.logging.log4j:log4j-core safe? maven package security report | CyberXYZ