Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

GHSA-8489-44mv-ggj8

MEDIUM

Improper Input Validation and Injection in Apache Log4j2

Also known asCVE-2021-44832
Published
Jan 4, 2022
Updated
Jun 9, 2026
Affected
7 pkgs
Patched
7 / 7
Exploits
3 known

EPSS Exploitation Probability

via FIRST.org ↗
53.6%probability of exploitation in next 30 days
High Risk98th percentile-0.06%
29.7%39.5%49.3%59.2%35.2%53.6%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

7 pkgs affected
org.apache.logging.log4j:log4j-coreorg.apache.logging.log4j:log4j-coreorg.apache.logging.log4j:log4j-coreorg.ops4j.pax.logging:pax-logging-log4j2org.ops4j.pax.logging:pax-logging-log4j2org.ops4j.pax.logging:pax-logging-log4j2org.ops4j.pax.logging:pax-logging-log4j2

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are vulnerable to an attack where an attacker with permission to modify the logging configuration file can construct a malicious configuration using a JDBC Appender with a data source referencing a JNDI URI which can execute remote code. This issue is fixed by limiting JNDI data source names to the java protocol in Log4j2 versions 2.17.1, 2.12.4, and 2.3.2.

Affected packages

Only the org.apache.logging.log4j:log4j-core package is directly affected by this vulnerability. The org.apache.logging.log4j:log4j-api should be kept at the same version as the org.apache.logging.log4j:log4j-core package to ensure compatability if in use.

This issue does not impact default configurations of Log4j2 and requires an attacker to have control over the Log4j2 configuration, which reduces the likelihood of being exploited.

Affected Packages

7 total 7 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.apache.logging.log4j:log4j-core2.0-beta7&&< 2.3.22.3.2
Mavenorg.apache.logging.log4j:log4j-core2.4&&< 2.12.42.12.4
Mavenorg.apache.logging.log4j:log4j-core2.13.0&&< 2.17.12.17.1
Mavenorg.ops4j.pax.logging:pax-logging-log4j21.8.0&&< 1.9.21.9.2
Mavenorg.ops4j.pax.logging:pax-logging-log4j21.10.0&&< 1.10.91.10.9
Mavenorg.ops4j.pax.logging:pax-logging-log4j21.11.0&&< 1.11.131.11.13
Exploits & PoCs
3

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Frequently Asked Questions

Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are vulnerable to an attack where an attacker with permission to modify the logging configuration file can construct a malicious configuration using a JDBC Appender with a data source referencing a JNDI URI which can execute remote code. This issue is fixed by limiting JNDI data source names to the java protocol in Log4j2 versions 2.17.1, 2.12.4, and 2.3.2. # Affected packages Only the `org.apache.logging.log4j:log4j-core` package is directly affected by this vulnerability. The `org.apache.logg
O3 Security · Impact-Aware SCA

Is GHSA-8489-44mv-ggj8 in your stack?

O3 detects GHSA-8489-44mv-ggj8 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.