Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Versions log4j:log4j up to and including 1.2.17 and org.zenframework.z8.dependencies.commons:log4j-1.2.17 up to and including 2.0 are affected. The issue only arises when the JDBCAppender is configured, since its SQL statement can include logged message content; an attacker who can get crafted strings into application input or headers that get logged can cause unintended SQL to run. No fixed version is listed for either package. Log4j 1.2 is end of life, so the source recommends moving to Log4j 2, and the source gives no other workaround beyond not using the JDBCAppender.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 9.8 | Critical | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | GitHub Advisory Database |
- CISA KEV Not listed.
- EPSS 0.67, the 99th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:20 UTC First seen by agentprime
- 31 Oct 2026, 14:20 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-65fg-84f6-3jq3
- OSV: GHSA-65fg-84f6-3jq3
- nvd.nist.gov/vuln/detail/CVE-2022-23305
- github.com/apache/logging-log4j1
- lists.apache.org/thread/pt6lh3pbsvxqlwlp4c5l798dv2hkc85y
- logging.apache.org/log4j/1.2/index.html
- security.netapp.com/advisory/ntap-20220217-0007
- www.oracle.com/security-alerts/cpuapr2022.html
- www.oracle.com/security-alerts/cpujul2022.html
- www.openwall.com/lists/oss-security/2022/01/18/4