Vulnerability Database · Maven · log4j:log4j · Version
log4j:log4j 1.2.9
1.2.9 is affected by 5 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 3 High 2 Medium 0 Low 0 Unrated 0
-
Released 22 Nov 2005
Licence Apache-2.0
Also known from other sources 6
Newer releases 14
Database updated 23/Oct/2026
Release and licence data published by Maven Central. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
log4j:log4j 1.2.9 vulnerabilities
5 vulnerabilities cover log4j:log4j 1.2.9. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2022-23305: SQL Injection in Log4j 1.2.x | 9.8 critical | No fix published | 21 Jan 2022 |
| CVE-2022-23307: Apache Log4j Deserialization of Untrusted Data | 9.8 critical | No fix published | 19 Jan 2022 |
| CVE-2019-17571: Log4j Deserialization of Untrusted Data | 9.8 critical | No fix published | 06 Jan 2020 |
| CVE-2022-23302: Log4j 1.x Deserialization of Untrusted Data | 8.8 high | No fix published | 21 Jan 2022 |
| CVE-2021-4104: Log4j 1.2 JMSAppender Deserialization Vulnerability | 7.5 high | No fix published | 14 Dec 2021 |
Looking for another version, or everything Vulert holds for log4j:log4j?
Questions
About log4j:log4j 1.2.9
Is log4j:log4j 1.2.9 vulnerable?
Yes. 5 vulnerabilities in the Vulert database cover log4j:log4j 1.2.9: 3 critical, 2 high, 0 medium and 0 low. Each entry above names the fixed version to move to.
Is 1.2.9 the latest release of log4j:log4j?
No. 1.2.9 was published 22 Nov 2005, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor log4j:log4j for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the log4j:log4j version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.