Which products and versions are affected by CVE-2022-4223?

Affected: Pgadmin 4; Fedora (Fedoraproject) versions 37; pgadmin4 (pypi) versions >= pgadmin4 6.17. The full list is in the CVE brief.

Is CVE-2022-4223 being exploited in the wild?

It is not listed in any known-exploited vulnerabilities catalog.

Is CVE-2022-4223 in the CISA KEV catalog?

No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.

Is there a public exploit for CVE-2022-4223?

No public exploit code is known.

Is there a fix for CVE-2022-4223?

Fixed versions are available, including Pgadmin 4 6.17, pgadmin4 6.17.

How urgently should CVE-2022-4223 be patched?

Brandefense priority: patch immediately, because it is very likely to be exploited soon.

Request A Demo

Vulnerability Intelligence

CVE-2022-4223

High

pgadmin4 vulnerable to Code Injection

Published Dec 13, 2022 · Updated Aug 12, 2026 · Also known as GHSA-3v6v-2x6p-32mc, PYSEC-2026-893

Key Facts

Patch immediately

CVE-2022-4223 is a high-severity vulnerability (CVSS 8.8 v3.1) affecting Pgadmin 4, Fedora (Fedoraproject), pgadmin4 (pypi).
It is not listed in any known-exploited vulnerabilities catalog. No public exploit code is known.
EPSS estimates a 80% probability of exploitation in the next 30 days.
Fixed versions are available, including Pgadmin 4 6.17, pgadmin4 6.17.
Brandefense priority: patch immediately, because it is very likely to be exploited soon.

CVSS v3.1

8.8

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS (30-day exploit likelihood)

80%

Higher than 99.6% of all scored CVEs

Exploited in the wild

No known

Not in a known-exploited catalog

Public exploit code

None known

Get the full CVE-2022-4223 brief as a PDF

Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.

Description

The pgAdmin server includes an HTTP API that is intended to be used to validate the path a user selects to external PostgreSQL utilities such as pg_dump and pg_restore. The utility is executed by the server to determine what PostgreSQL version it is from. Versions of pgAdmin prior to 6.17 failed to properly secure this API, which could allow an unauthenticated user to call it with a path of their choosing, such as a UNC path to a server they control on a Windows machine. This would cause an appropriately named executable in the target path to be executed by the pgAdmin server.

Affected Products

4 affected entries in total

Product	Affected versions	Fixed in
Pgadmin 4Pgadmin	See advisory	6.17
FedoraFedoraproject	37	n/a
pgadmin4pypi	>= pgadmin4 6.17	6.17

Patched Releases

Pgadmin 4

6.17

pgadmin4

6.17

Timeline

Publicly disclosed
Dec 13, 2022
Last updated
Aug 12, 2026

Weakness Type

CWE-94 Improper Control of Generation of Code ('Code Injection')
CWE-862 Missing Authorization

References

4 more references in the full CVE brief

FAQ

Common Questions.

The pgAdmin server includes an HTTP API that is intended to be used to validate the path a user selects to external PostgreSQL utilities such as pg_dump and pg_restore.
Affected: Pgadmin 4; Fedora (Fedoraproject) versions 37; pgadmin4 (pypi) versions >= pgadmin4 6.17. The full list is in the CVE brief.
It is not listed in any known-exploited vulnerabilities catalog.
No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
No public exploit code is known.
Fixed versions are available, including Pgadmin 4 6.17, pgadmin4 6.17.
Brandefense priority: patch immediately, because it is very likely to be exploited soon.

Is CVE-2022-4223 Running On Your Attack Surface?

Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.