Apache LOG4J 1.x
4 CVEs tracked. None of them is in CISA KEV.
This hub aggregates every CVE we track for Apache LOG4J 1.x, a product in the oss libraries space. Use it to gauge the current risk picture and drill into individual advisories.
Apache LOG4J 1.x CVEs per month
| Month | CVEs |
|---|---|
| 2024-10 | 0 |
| 2024-11 | 0 |
| 2024-12 | 0 |
| 2025-01 | 0 |
| 2025-02 | 0 |
| 2025-03 | 0 |
| 2025-04 | 0 |
| 2025-05 | 0 |
| 2025-06 | 0 |
| 2025-07 | 0 |
| 2025-08 | 0 |
| 2025-09 | 0 |
| 2025-10 | 0 |
| 2025-11 | 0 |
| 2025-12 | 0 |
| 2026-01 | 0 |
| 2026-02 | 0 |
| 2026-03 | 0 |
| 2026-04 | 0 |
| 2026-05 | 0 |
| 2026-06 | 0 |
| 2026-07 | 0 |
| 2026-08 | 0 |
| 2026-09 | 0 |
Severity
How the 4 CVEs score on CVSS. Severity is not exploitation: KEV is counted above.
- Critical1
- High3
Latest CVEs
The 4 most recently published vulnerabilities affecting Apache LOG4J 1.x.
- CVE-2022-23307A deserialization flaw in the Chainsaw component of Log4j 1 can lead to malicious code execution.8.8
- CVE-2022-23305SQL injection in JDBC Appender in Apache Log4j V19.8
- CVE-2022-23302Deserialization of untrusted data in JMSSink in Apache Log4j 1.x8.8
- CVE-2021-4104Deserialization of untrusted data in JMSAppender in Apache Log4j 1.27.5
Product grouping is registry-driven, with AI assist and human review. How it works