Advisory record · GHSA-65fg-84f6-3jq3

SQL Injection in Log4j 1.2.x

CVSS 9.8 CriticalCriticalEPSS 0.67 · 99th percentile

Critical, because:

  • CVSS score 9.8: 9.0 or more.
  • CVSS score 9.8 (7.0 or more) and EPSS 0.67 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical

Published by the GitHub Advisory Database at 21 Jan 2022, 23:26 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
log4j:log4jMaven<=1.2.17No fixed version yet
org.zenframework.z8.dependencies.commons:log4j-1.2.17Maven<=2.0No fixed version yet
Identifiers
GHSA-65fg-84f6-3jq3 · CVE-2022-23305
Weakness (CWE)
CWE-89
Published
21 Jan 2022
Updated
8 Jun 2026

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.

Written 3 Nov 2026.

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

ScoreRatingCVSSVectorSource
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

  1. 31 Oct 2026, 14:20 UTC First seen by agentprime
  2. 31 Oct 2026, 14:20 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.