Technology · Maven
log4j:log4j (Maven) vulnerabilities
Updated . Rebuilt every hour.
Junglewise Threat Intelligence has tracked 6 vulnerabilities in log4j:log4j (Maven): 0 in the last 7 days and 0 in the last 90 days, 2 of them critical and 0 exploited in the wild. The most recent, CVE-2023-26464, was published on 10 March 2023.
- Last 7 days
- 0
- Last 90 days
- 0
- Critical, all time
- 2
- Exploited in the wild
- 0
About log4j:log4j (Maven)
A legacy Java-based logging utility used to output log statements to various targets.
Latest log4j:log4j (Maven) vulnerabilities
- CVE-2023-26464: Apache Log4j 1.x (EOL) allows Denial of Service (DoS)lowCVSS 3.1EPSS 1.9%
- CVE-2022-23302: Deserialization of Untrusted Data in Log4j 1.xlowCVSS 3.1EPSS 63.6%
- CVE-2022-23305: Apache Log4j SQL injection in JDBCAppendercriticalCVSS 9.8EPSS 66.5%
- CVE-2022-23307: Deserialization of Untrusted Data in Apache Log4jlowCVSS 3.1EPSS 54.4%
- CVE-2021-4104: JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted datalowCVSS 3.1EPSS 80.6%
- CVE-2019-17571: Apache Log4j deserialization in SocketServercriticalCVSS 9.8EPSS 69.1%
Most severe log4j:log4j (Maven) vulnerabilities
Exploited in the wild first, then by severity and CVSS score.
- CVE-2019-17571: Apache Log4j deserialization in SocketServercriticalCVSS 9.8EPSS 69.1%
- CVE-2022-23305: Apache Log4j SQL injection in JDBCAppendercriticalCVSS 9.8EPSS 66.5%
- CVE-2021-4104: JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted datalowCVSS 3.1EPSS 80.6%
- CVE-2022-23302: Deserialization of Untrusted Data in Log4j 1.xlowCVSS 3.1EPSS 63.6%
- CVE-2022-23307: Deserialization of Untrusted Data in Apache Log4jlowCVSS 3.1EPSS 54.4%
- CVE-2023-26464: Apache Log4j 1.x (EOL) allows Denial of Service (DoS)lowCVSS 3.1EPSS 1.9%
Vulnerabilities per week
Nothing was published in the last eight weeks. The last 13 weeks, by the week each vulnerability was published.
| Week of | Bar | Vulns | Critical |
|---|---|---|---|
| 17 Aug 2026 | 0 | 0 | |
| 24 Aug 2026 | 0 | 0 | |
| 31 Aug 2026 | 0 | 0 | |
| 7 Sep 2026 | 0 | 0 | |
| 14 Sep 2026 | 0 | 0 | |
| 21 Sep 2026 | 0 | 0 | |
| 28 Sep 2026 | 0 | 0 | |
| 5 Oct 2026 | 0 | 0 | |
| 12 Oct 2026 | 0 | 0 | |
| 19 Oct 2026 | 0 | 0 | |
| 26 Oct 2026 | 0 | 0 | |
| 2 Nov 2026 | 0 | 0 | |
| 9 Nov 2026 | 0 | 0 |
Embed a badge
A live badge for a README, a status page or an internal wiki: how many log4j:log4j (Maven) vulnerabilities were published in the last 7 days and how many of them are critical, refreshed hourly.
[](https://junglewise.ai/threats/technologies/log4j-log4j)<a href="https://junglewise.ai/threats/technologies/log4j-log4j"><img src="https://junglewise.ai/threats/technologies/log4j-log4j/badge.svg" alt="log4j:log4j (Maven) vulnerabilities" /></a>How this is built
Junglewise Threat Intelligence collects vulnerabilities from NVD, GitHub Security Advisories, OSV, the CISA Known Exploited Vulnerabilities catalog, FIRST EPSS and vendor advisories, and matches each one to the technologies and vendors it affects. Dates are the date a vulnerability was published, in UTC.
The pages are rebuilt from the database every hour. Frozen weekly and monthly reports never change once published, so they can be cited.
Use this data
The same data is at https://junglewise.ai/threats/technologies/log4j-log4j.json, and this page as text at https://junglewise.ai/threats/technologies/log4j-log4j.md, for scripts and language models. It is free to reuse under CC BY 4.0 with a link back to this page.
Cite as: Junglewise Threat Intelligence, "log4j:log4j (Maven) vulnerabilities", https://junglewise.ai/threats/technologies/log4j-log4j, 9 November 2026.