Skip to content
Fencer Vulns
critical 9.8

CVE-2022-26520 json

pgjdbc Arbitrary File Write Vulnerability

published 2022-02-16 4 y ago modified 2026-09-10 1 mo ago also BIT-postgresql-jdbc-driver-2022-26520 , EUVD-2022-1351 , GHSA-673j-qm5f-xpv8 , GHSA-727h-hrw8-jg8q

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.0%
EPSS 3.0% chance of exploitation in 30 days, percentile 87%
public exploits
0
none known

Summary

In pgjdbc before 42.3.3, an attacker (who controls the jdbc URL or properties) can call java.util.logging.FileHandler to write to arbitrary files through the loggerFile and loggerLevel connection properties. An example situation is that an attacker could create an executable JSP file under a Tomcat web root. NOTE: the vendor's position is that there is no pgjdbc vulnerability; instead, it is a vulnerability for any application to use the pgjdbc driver with untrusted connection properties

Patch / fix

  • maven org.postgresql:postgresql 42.3.3
  • bitnami postgresql-jdbc-driver 42.1.5, 42.3.3
  • postgresql postgresql_jdbc_driver 42.3.3
  • libpgjava Debian 14, Debian 13, Debian 12 42.3.3-1

debian advisories DEBIAN-CVE-2022-26520

  • postgresql-jdbc SLE Module for Server Applications 15 SP3, openSUSE Leap 15.3, Manager Server Module 4.2 42.2.25-150300.3.5.2
  • ongres-scram SLE Module for Server Applications 15 SP3, openSUSE Leap 15.3, Manager Server Module 4.2 2.1-150300.3.3.4
  • ongres-stringprep SLE Module for Server Applications 15 SP3, openSUSE Leap 15.3, Manager Server Module 4.2 1.1-150300.7.3.4
  • postgresql-jdbc SLE Module for Server Applications 15 SP4, openSUSE Leap 15.4 42.2.25-150400.3.3.2
  • spacecmd Manager Server Module 4.1 4.1.18-150200.4.39.3
  • susemanager Manager Server Module 4.1 4.1.36-150200.3.52.1
  • spacewalk-web Manager Server Module 4.1 4.1.34-150200.3.47.6
  • spacewalk-java Manager Server Module 4.1 4.1.46-150200.3.71.5

suse advisories SUSE-FU-2022:2794-1SUSE-SU-2022:2655-1SUSE-SU-2022:2145-1SUSE-SU-2022:2143-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-26520 updated cvss 9.8

postgresql-jdbc: Arbitrary File Write Vulnerability

  • Red Hat build of Debezium 1 jdbc-postgresql jdbc-postgresql
    affected: no fix available
  • Red Hat Enterprise Linux 6 postgresql-jdbc Red Hat Enterprise Linux 7 postgresql-jdbc, postgresql-jdbc-javadoc
    affected: no fix planned “Out of support scope”
  • Red Hat Integration Camel K 1 jdbc-postgresql jdbc-postgresql
    affected: no fix planned “Will not fix”
  • Red Hat Integration Data Virtualisation Operator jdbc-postgresql jdbc-postgresql
    affected: no fix planned “Out of support scope”
  • Red Hat Fuse 7.11
    fixed: vendor fix RHSA-2022:5532
  • Red Hat RHINT Service Registry 2.3.0 GA
    fixed: vendor fix RHSA-2022:6835
  • Red Hat RHPAM 7.13.1 async
    fixed: vendor fix RHSA-2022:6813
  • Red Hat build of Quarkus quarkus-jdbc-postgresql Red Hat Enterprise Linux 8 postgresql-jdbc, postgresql-jdbc-javadoc Red Hat Enterprise Linux 9 postgresql-jdbc Red Hat Integration Camel Quarkus 1 jdbc-postgresql jdbc-postgresql
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

3.00% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
OSV 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.postgresql:postgresql
>=42.1.0, <42.3.3
42.3.3
bitnami postgresql-jdbc-driver
>=42.1.0, <42.1.5
>=42.3.0, <42.3.3
42.1.5
42.3.3

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.