Is com.guicedee.services:log4j-core 1.2 vulnerable?
Maven · 4 releases from 1.2.0 to 1.2.2.1 · latest com.guicedee.services:log4j-core is 1.2.2.1-jre17 · checked 18 Nov 2026
No known advisories in the last release
com.guicedee.services:log4j-core 1.2.2.1, the last 1.2 release, has no known advisories. 1 advisory affects earlier 1.2.x releases, so update to 1.2.2.1.
mvn versions:use-dep-version -Dincludes=com.guicedee.services:log4j-core -DdepVersion=1.2.2.1 -DforceVersion=trueIs your project on an affected com.guicedee.services:log4j-core?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 1.2.x, affecting earlier releases
Remote code injection in Log4j
- Affected
- <=1.2.1.2-jre17
- Fixed in
- No fix released
Every com.guicedee.services:log4j-core 1.2.x release
Affected: 1.2.0 to 1.2.1. 1.2.2 and later are not affected. Latest com.guicedee.services:log4j-core: 1.2.2.1-jre17.
| Version | Known advisories |
|---|---|
| com.guicedee.services:log4j-core 1.2.2.1 | None |
| com.guicedee.services:log4j-core 1.2.2 | None |
| com.guicedee.services:log4j-core 1.2.1 | CVE-2021-44228 |
| com.guicedee.services:log4j-core 1.2.0 | CVE-2021-44228 |
Which of your client projects are still on com.guicedee.services:log4j-core 1.2?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact com.guicedee.services:log4j-core version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other com.guicedee.services:log4j-core versions
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.