Is org.apache.logging.log4j:log4j 2.19 vulnerable?
Maven · 1 release from 2.19.0 to 2.19.0 · latest org.apache.logging.log4j:log4j is 2.26.1 · checked 18 Nov 2026
No known advisories in the last release
No. No org.apache.logging.log4j:log4j 2.19.x release has a known security advisory.
Is your project on an affected org.apache.logging.log4j:log4j?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Which of your client projects are still on org.apache.logging.log4j:log4j 2.19?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact org.apache.logging.log4j:log4j version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other org.apache.logging.log4j:log4j versions
- org.apache.logging.log4j:log4j 2.22
- org.apache.logging.log4j:log4j 2.21
- org.apache.logging.log4j:log4j 2.20
- org.apache.logging.log4j:log4j 2.18
- org.apache.logging.log4j:log4j 2.17
- org.apache.logging.log4j:log4j 2.16
- org.apache.logging.log4j:log4j 2.26
- org.apache.logging.log4j:log4j 2.25
- org.apache.logging.log4j:log4j 2.24
- org.apache.logging.log4j:log4j 2.23
- All org.apache.logging.log4j:log4j advisories
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.