CVE-2022-4223

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 79.9%, top 0% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this weekElevated
8.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 80%
CISA-KEV: Not listedEPSS: 80%CVSS: 8.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
99.6%
KEV
Not listed

Published

December 13, 2022

Last Modified

April 14, 2025

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
pgadmin44.20 ... 6.9 (33 versions)6.17

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 22× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-22 23:01 UTCEG score recompute 0.20
  2. 2026-07-22 14:06 UTCEPSS rescore
  3. 2026-07-22 14:06 UTCEPSS rescore
  4. 2026-07-20 17:05 UTCEPSS rescore
  5. 2026-07-19 02:27 UTCEPSS rescore
  6. 2026-07-19 02:27 UTCEPSS rescore
  7. 2026-07-16 12:49 UTCOSV refresh
  8. 2026-07-15 16:56 UTCEPSS rescore
  9. 2026-07-15 16:56 UTCEPSS rescore
  10. 2026-07-12 05:44 UTCEPSS rescore
  11. 2026-07-08 15:13 UTCEPSS rescore
  12. 2026-07-04 06:29 UTCEPSS rescore
  13. 2026-07-01 15:04 UTCEPSS rescore
  14. 2026-06-28 11:49 UTCOSV refresh
  15. 2026-06-28 04:54 UTCEPSS rescore
  16. 2026-06-28 04:54 UTCEPSS rescore
  17. 2026-06-25 13:48 UTCEPSS rescore
  18. 2026-06-25 13:48 UTCEPSS rescore
  19. 2026-06-24 14:03 UTCEPSS rescore
  20. 2026-06-24 14:03 UTCEPSS rescore
  21. 2026-06-23 21:31 UTCEPSS rescore
  22. 2026-06-23 21:31 UTCEPSS rescore
  23. 2026-06-21 01:58 UTCEPSS rescore
  24. 2026-06-21 01:58 UTCEPSS rescore
  25. 2026-06-17 17:51 UTCEPSS rescore
Show 28 more
  1. 2026-06-17 17:51 UTCEPSS rescore
  2. 2026-06-15 17:47 UTCEPSS rescore
  3. 2026-06-13 22:59 UTCEPSS rescore
  4. 2026-06-12 23:10 UTCEPSS rescore
  5. 2026-06-12 23:10 UTCEPSS rescore
  6. 2026-06-11 13:58 UTCEPSS rescore
  7. 2026-06-11 13:58 UTCEPSS rescore
  8. 2026-06-10 22:14 UTCOSV refresh
  9. 2026-06-10 13:21 UTCEPSS rescore
  10. 2026-06-10 13:21 UTCEPSS rescore
  11. 2026-06-08 14:15 UTCEPSS rescore
  12. 2026-06-08 14:15 UTCEPSS rescore
  13. 2026-06-07 15:23 UTCEPSS rescore
  14. 2026-06-07 15:23 UTCEPSS rescore
  15. 2026-06-05 22:46 UTCEPSS rescore
  16. 2026-06-05 22:46 UTCEPSS rescore
  17. 2026-06-05 06:09 UTCEPSS rescore
  18. 2026-06-05 06:09 UTCEPSS rescore
  19. 2026-06-04 13:11 UTCEPSS rescore
  20. 2026-06-01 13:50 UTCEPSS rescore
  21. 2026-06-01 13:50 UTCEPSS rescore
  22. 2026-05-29 13:43 UTCEPSS rescore
  23. 2026-05-28 13:43 UTCEPSS rescore
  24. 2026-05-28 13:43 UTCEPSS rescore
  25. 2026-05-26 07:17 UTCEPSS rescore
  26. 2026-05-26 07:17 UTCEPSS rescore
  27. 2026-05-26 07:17 UTCEPSS rescore
  28. 2026-05-25 10:41 UTCEG score recompute

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2022/CVE-2022-4223.yaml
    First seen Jan 1, 2022

    pgAdmin < 6.17 - Unauthenticated Remote Code Execution

    Open source ↗

Frequently asked(5)

What is CVE-2022-4223?
CVE-2022-4223 is a high vulnerability published on December 13, 2022. 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 pgdump and pgrestore. The utility is executed by the server to determine what PostgreSQL version it is from. Versions of pgAdmin prior to 6.17 failed to…
When was CVE-2022-4223 disclosed?
CVE-2022-4223 was first published in the National Vulnerability Database on December 13, 2022, with the most recent update on April 14, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-4223 actively exploited?
CVE-2022-4223 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2022-4223?
CVE-2022-4223 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2022-4223?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-4223, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-4223

Explore →

Is Your Infrastructure Affected by CVE-2022-4223?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.