PostgreSQL JDBC Driver (PgJDBC for short) allows Java programs to connect to a PostgreSQL database using standard, database independent Java code. The PGJDBC implementation of the java.sql.ResultRow.refreshRow() method is not performing escaping of column names so a malicious column name that contains a statement terminator, e.g. ;, could lead to SQL injection. This could lead to executing additional SQL commands as the application's JDBC user. User applications that do not invoke the ResultSet.refreshRow() method are not impacted. User application that do invoke that method are impacted if the underlying database that they are querying via their JDBC application may be under the control of an attacker. The attack requires the attacker to trick the user into executing SQL against a table name who's column names would contain the malicious SQL and subsequently invoke the refreshRow() method on the ResultSet. Note that the application's JDBC user and the schema owner need not be the same. A JDBC application that executes as a privileged user querying database schemas owned by potentially malicious less-privileged users would be vulnerable. In that situation it may be possible for the malicious user to craft a schema that causes the application to execute commands as the privileged user. Patched versions will be released as 42.2.26 and 42.4.1. Users are advised to upgrade. There are no known workarounds for this issue.
CVE-2022-31197
“—” beside the score: it is equal to NVD's CVSS score.
This high-severity CVE scores 7.1 under NVD CVSS v3. EPSS exploit probability: 2.4% (83rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 7.1
- EG Score
- 7.1HIGHmedium confidence
- EG Risk
- 48EG Risk 48/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity71% × 45%Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 2.4%
- EPSS %ILE
- 83rd
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
- EG Likelihood
- 2.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-20). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
August 3, 2022
Last Modified
November 3, 2025
References (6)
- security-advisories@github · CVE Programhttps://github.com/pgjdbc/pgjdbc/commit/739e599d52ad80f8dcd6efedc6157859b1a9d637Patch · Third Party Advisory
- security-advisories@github · CVE Programhttps://github.com/pgjdbc/pgjdbc/security/advisories/GHSA-r38f-c4h4-hqq2Exploit · Third Party Advisory
- security-advisories@github · CVE Programhttps://lists.debian.org/debian-lts-announce/2022/10/msg00009.htmlMailing List · Third Party Advisory
- security-advisories@github · CVE Programhttps://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/I6WHUADTZBBQLVHO4YG4XCWDGWBT4LRP/
- security-advisories@github · CVE Programhttps://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/UTFE6SV33P5YYU2GNTQZQKQRVR3GYE4S/
- CVE Programhttps://lists.debian.org/debian-lts-announce/2024/12/msg00017.html
Vendor Advisories for CVE-2022-31197(4)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2023:1006Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat build of Quarkus 2.7.7 release and security update
- RHSA-2023:0318Red Hat Product SecurityMedium
Red Hat Security Advisory: postgresql-jdbc security update
- RHSA-2022:9023Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat build of Quarkus 2.13.5 release and security update
- RHSA-2022:8652Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Fuse 7.11.1 release and security update
Patch Availability(4)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| redhat | patch | 2023-03-08 | redhat |
| redhat | postgresql-jdbc-0:42.2.18-6.el9_1 | 2023-01-23 | redhat |
| redhat | postgresql | 2022-12-14 | redhat |
| redhat | jdbc-postgresql | 2022-11-28 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(6 across 6 ecosystems)
Debian:10(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| libpgjava | 42.2.5-2, 42.2.5-2+deb10u1 |
| — |
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| libpgjava | 42.2.15-1, 42.2.15-1+deb11u1 |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| libpgjava | — |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| libpgjava | — |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| libpgjava | — |
| — |
Maven(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| org.postgresql:postgresql | 42.3.0 ... 42.3.6 (7 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 37× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 97 of 203 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 106 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-23 16:28 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
- 2026-10-22 16:30 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
- 2026-10-21 16:28 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
- 2026-10-21 07:20 UTCEG score recompute
- 2026-10-21 07:20 UTCVendor advisory
- 2026-10-20 16:29 UTCEPSS rescoreEPSS 2.4% · 83rd percentile
- 2026-10-19 16:28 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
- 2026-10-18 16:28 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
- 2026-10-18 08:35 UTCEG score recompute
- 2026-10-17 16:29 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
- 2026-10-16 16:34 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
- 2026-10-16 06:54 UTCOSV refresh
- 2026-10-15 16:28 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
- 2026-10-14 16:29 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
- 2026-10-13 16:29 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
- 2026-10-12 18:54 UTCEG score recompute
- 2026-10-12 16:30 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
- 2026-10-11 23:18 UTCEG score recompute
- 2026-10-11 13:44 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
- 2026-10-10 19:56 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
- 2026-10-09 20:04 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
- 2026-10-08 16:40 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
- 2026-10-07 23:45 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
- 2026-10-06 15:14 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
- 2026-10-05 17:40 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
Show 72 moreShow fewer
- 2026-10-04 23:19 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
- 2026-10-03 14:23 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
- 2026-10-02 16:23 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
- 2026-09-30 15:55 UTCEG score recompute
- 2026-09-30 15:00 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
- 2026-09-29 15:16 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
- 2026-09-28 13:48 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
- 2026-09-27 13:42 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
- 2026-09-26 15:54 UTCEPSS rescoreEPSS 2.1% · 80th percentile
- 2026-09-26 00:22 UTCEPSS rescoreEPSS 2.1% · 80th percentile
- 2026-09-24 15:16 UTCOSV refresh
- 2026-09-24 14:00 UTCEPSS rescoreEPSS 2.1% · 80th percentile
- 2026-09-23 13:45 UTCEPSS rescoreEPSS 2.1% · 80th percentile
- 2026-09-22 14:44 UTCEPSS rescoreEPSS 2.1% · 80th percentile
- 2026-09-20 20:13 UTCEPSS rescoreEPSS 2.1% · 80th percentile
- 2026-09-19 15:38 UTCEPSS rescoreEPSS 2.1% · 80th percentile
- 2026-09-18 19:24 UTCEPSS rescoreEPSS 2.1% · 80th percentile
- 2026-09-16 14:05 UTCEPSS rescoreEPSS 2.1% · 80th percentile
- 2026-09-15 03:06 UTCEPSS rescoreEPSS 2.1% · 80th percentile
- 2026-09-12 14:57 UTCEPSS rescoreEPSS 2.1% · 80th percentile
- 2026-09-11 14:49 UTCEPSS rescoreEPSS 2.1% · 80th percentile
- 2026-09-11 09:33 UTCEPSS rescoreEPSS 2.1% · 80th percentile
- 2026-09-08 21:57 UTCEPSS rescoreEPSS 2.1% · 80th percentile
- 2026-09-07 15:58 UTCEPSS rescoreEPSS 2.1% · 80th percentile
- 2026-09-06 13:45 UTCEPSS rescoreEPSS 2.1% · 80th percentile
- 2026-09-05 15:25 UTCEPSS rescoreEPSS 2.1% · 80th percentile
- 2026-09-05 07:48 UTCOSV refresh
- 2026-09-04 13:57 UTCEPSS rescoreEPSS 2.1% · 80th percentile
- 2026-09-04 05:04 UTCEPSS rescoreEPSS 2.1% · 80th percentile
- 2026-09-02 14:09 UTCEPSS rescoreEPSS 2.1% · 80th percentile
- 2026-09-01 13:51 UTCEPSS rescoreEPSS 2.1% · 80th percentile
- 2026-08-30 19:14 UTCEPSS rescoreEPSS 2.1% · 80th percentile
- 2026-08-30 01:19 UTCEPSS rescoreEPSS 2.1% · 79th percentile
- 2026-08-28 21:38 UTCEPSS rescoreEPSS 2.1% · 79th percentile
- 2026-08-27 14:22 UTCEPSS rescoreEPSS 2.1% · 80th percentile
- 2026-08-26 14:43 UTCEPSS rescoreEPSS 2.1% · 80th percentile
- 2026-08-25 13:46 UTCEPSS rescoreEPSS 2.1% · 80th percentile
- 2026-08-24 14:13 UTCEPSS rescoreEPSS 2.1% · 80th percentile
- 2026-08-23 00:16 UTCEPSS rescoreEPSS 2.1% · 80th percentile
- 2026-08-21 23:46 UTCEPSS rescoreEPSS 2.1% · 80th percentile
- 2026-08-20 22:52 UTCEPSS rescoreEPSS 2.1% · 80th percentile
- 2026-08-19 17:01 UTCEPSS rescoreEPSS 2.1% · 80th percentile
- 2026-08-18 18:28 UTCOSV refresh
- 2026-08-18 13:45 UTCEPSS rescoreEPSS 2.1% · 79th percentile
- 2026-08-17 13:44 UTCEPSS rescoreEPSS 2.1% · 79th percentile
- 2026-08-16 14:53 UTCEPSS rescoreEPSS 2.1% · 79th percentile
- 2026-08-16 02:11 UTCEPSS rescoreEPSS 2.1% · 79th percentile
- 2026-08-15 01:27 UTCEPSS rescoreEPSS 2.1% · 79th percentile
- 2026-08-13 21:57 UTCEPSS rescoreEPSS 2.1% · 79th percentile
- 2026-08-12 13:48 UTCEPSS rescoreEPSS 2.1% · 79th percentile
- 2026-08-11 13:38 UTCEPSS rescoreEPSS 2.1% · 79th percentile
- 2026-08-09 13:44 UTCEPSS rescoreEPSS 2.1% · 79th percentile
- 2026-08-08 16:34 UTCEPSS rescoreEPSS 2.1% · 79th percentile
- 2026-08-07 16:24 UTCEPSS rescoreEPSS 2.1% · 79th percentile
- 2026-08-06 13:44 UTCEPSS rescoreEPSS 2.1% · 79th percentile
- 2026-08-05 19:15 UTCEPSS rescoreEPSS 2.1% · 79th percentile
- 2026-08-04 15:07 UTCEPSS rescoreEPSS 2.1% · 79th percentile
- 2026-08-04 10:35 UTCEPSS rescoreEPSS 2.1% · 79th percentile
- 2026-08-03 14:27 UTCOSV refresh
- 2026-08-03 10:33 UTCEPSS rescoreEPSS 2.1% · 79th percentile
- 2026-08-02 02:24 UTCEPSS rescoreEPSS 2.1% · 79th percentile
- 2026-08-01 04:13 UTCEPSS rescoreEPSS 2.1% · 79th percentile
- 2026-07-30 16:25 UTCEPSS rescoreEPSS 1.7% · 74th percentile
- 2026-07-30 01:28 UTCEPSS rescoreEPSS 1.7% · 74th percentile
- 2026-07-28 15:33 UTCEPSS rescoreEPSS 1.7% · 74th percentile
- 2026-07-26 14:52 UTCEPSS rescoreEPSS 1.7% · 74th percentile
- 2026-07-25 14:15 UTCEPSS rescoreEPSS 1.7% · 74th percentile
- 2026-07-24 14:15 UTCEPSS rescoreEPSS 1.7% · 74th percentile
- 2026-07-23 14:16 UTCEPSS rescoreEPSS 1.7% · 74th percentile
- 2026-07-23 02:11 UTCEG score recompute
- 2026-07-22 22:58 UTCEG score recompute
- 2026-07-22 14:06 UTCEPSS rescoreEPSS 1.7% · 74th percentile
Related CVEs(same product + same vendor + same CWE)
Same product
10 shownDebian:10:libpgjava · Debian:11:libpgjava · Maven:org.postgresql:postgresql
Same vendor
10 shownredhat:RHSA-2022:8652 · redhat:RHSA-2022:9023 · redhat:RHSA-2023:1006
- CVE-2022-42889EG 9.8EPSS p100CRITICAL
- CVE-2022-42004EG 7.5HIGH
- CVE-2022-42003EG 7.5HIGH
- CVE-2022-3171EG 4.3MEDIUM
- CVE-2022-4116EG 9.8EPSS p98CRITICAL
- CVE-2022-33980EG 9.8EPSS p99CRITICAL
- CVE-2021-44906EG 9.8EPSS p92CRITICAL
- CVE-2022-1471NVD 8.3EG 9.0EPSS p100CRITICAL
- CVE-2022-41966EG 8.2EPSS p95HIGH
- CVE-2022-41853EG 8.0EPSS p92HIGH
Same CWE
10 shownCWE-89
Frequently asked(5)
What is CVE-2022-31197?
When was the CVE record for CVE-2022-31197 published?
Is CVE-2022-31197 actively exploited?
What is the CVSS score of CVE-2022-31197?
How do I remediate CVE-2022-31197?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-31197
Is Your Infrastructure Affected by CVE-2022-31197?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.