VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

apache-log4j1.2: vulnerability history, versions and safety

apache-log4j1.2 is a package in the Debian ecosystem. Vulert records 11 vulnerabilities for it across 3 releases, from Dec 2019 to Apr 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
11 vulnerabilities recorded U11
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
1 in the last 12 months

Most recent disclosure 10 Apr 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all apache-log4j1.2 vulnerabilities

Vulert verdict on apache-log4j1.2 i

Updated on 23 Oct 2026

Careful: one of the 11 vulnerabilities Vulert records for this package has no fix yet. Plan around that one, or apply its workaround. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 11 vulnerabilities on record across 6 years, 1 in the last year.

What to do: Plan around the 1 vulnerability with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 11 over 6 years · 1 in the last year i
  • Latest disclosure 10 Apr 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 1 i

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 Versions

Which versions are affected

Every version Vulert holds for apache-log4j1.2, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
1.2.17-11 U1 No Details →
1.2.17-10 U9 No Details →
1.2.17-10+deb11u1 U1 No Details →

Newest 3 of 3 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 2
  • 2021 2
  • 2022 6
  • 2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 11 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for apache-log4j1.2

The 5 most severe of 11 vulnerabilities recorded for this package

Search all 11 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Remote Code Execution Vulnerability in Apache Log4j 1.2 - CVE-2019-17571 9.8 critical 1.2.17-9 20 Dec 2019
SQL Injection Risk in Log4j 1.2.x JDBCAppender Configuration 9.8 critical 1.2.17-10+deb11u1 18 Jan 2022
Critical Remote Code Execution Vulnerability in Log4j 1.x via JMSSink 8.8 high 1.2.17-10+deb11u1 18 Jan 2022
Deserialization Vulnerability in Apache Log4j 1.2 - CVE-2022-23307 8.8 high 1.2.17-10+deb11u1 18 Jan 2022
Remote Code Execution Vulnerability in Apache Log4j 1.2 via JMSAppender 7.5 high 1.2.17-10+deb11u1 14 Dec 2021

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About apache-log4j1.2

Is apache-log4j1.2 safe to use?

Vulert records 11 vulnerabilities for apache-log4j1.2 in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 11 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

How many vulnerabilities does apache-log4j1.2 have?

11 vulnerabilities are recorded for apache-log4j1.2 in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 11 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new apache-log4j1.2 vulnerabilities disclosed?

1 vulnerability was recorded for apache-log4j1.2 in the last 12 months, and the oldest entry in this database dates to 20 Dec 2019. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of apache-log4j1.2 are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor apache-log4j1.2 for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the apache-log4j1.2 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.