CVE-2024-3116

HIGHNVD 7.49.0
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 91% probability of exploitation within the next 30 days (top 0.4% of all CVEs). NVD baseline CVSS 7.4 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Weaponized
7.4
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 65%
CISA-KEV: Not listedEPSS: 65%CVSS: 7.4Exploit: NoneExposed: 0

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

pgAdmin <= 8.4 is affected by a Remote Code Execution (RCE) vulnerability through the validate binary path API. This vulnerability allows attackers to execute arbitrary code on the server hosting PGAdmin, posing a severe risk to the database management system's integrity and the security of the underlying data.

CVSS v3
7.4
EG Score
9.0(high)
EG Risk
EPSS
99.2%
KEV
Not listed

Published

April 4, 2024

Last Modified

March 17, 2025

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
pgadmin44.20 ... 8.4 (52 versions)8.5

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 30× 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 14:07 UTCEPSS rescore
  2. 2026-07-22 14:07 UTCEPSS rescore
  3. 2026-07-21 15:23 UTCEPSS rescore
  4. 2026-07-21 15:23 UTCEPSS rescore
  5. 2026-07-20 17:06 UTCEPSS rescore
  6. 2026-07-19 02:28 UTCEPSS rescore
  7. 2026-07-19 02:28 UTCEPSS rescore
  8. 2026-07-16 17:02 UTCEPSS rescore
  9. 2026-07-15 16:56 UTCEPSS rescore
  10. 2026-07-15 16:56 UTCEPSS rescore
  11. 2026-07-14 14:55 UTCOSV refresh
  12. 2026-07-13 22:29 UTCEPSS rescore
  13. 2026-07-12 05:45 UTCEPSS rescore
  14. 2026-07-11 08:26 UTCEPSS rescore
  15. 2026-07-11 08:26 UTCEPSS rescore
  16. 2026-07-09 19:09 UTCEPSS rescore
  17. 2026-07-06 02:22 UTCEPSS rescore
  18. 2026-07-06 02:22 UTCEPSS rescore
  19. 2026-07-01 15:05 UTCEPSS rescore
  20. 2026-06-29 14:05 UTCEPSS rescore
  21. 2026-06-28 14:06 UTCEPSS rescore
  22. 2026-06-28 14:06 UTCEPSS rescore
  23. 2026-06-28 04:55 UTCEPSS rescore
  24. 2026-06-28 04:55 UTCEPSS rescore
  25. 2026-06-27 03:07 UTCEPSS rescore
Show 32 more
  1. 2026-06-27 03:07 UTCEPSS rescore
  2. 2026-06-26 15:39 UTCOSV refresh
  3. 2026-06-25 13:49 UTCEPSS rescore
  4. 2026-06-23 21:32 UTCEPSS rescore
  5. 2026-06-23 21:32 UTCEPSS rescore
  6. 2026-06-18 17:52 UTCEPSS rescore
  7. 2026-06-18 17:51 UTCEPSS rescore
  8. 2026-06-17 17:52 UTCEPSS rescore
  9. 2026-06-16 17:52 UTCEPSS rescore
  10. 2026-06-16 17:52 UTCEPSS rescore
  11. 2026-06-15 17:47 UTCEPSS rescore
  12. 2026-06-13 22:59 UTCEPSS rescore
  13. 2026-06-13 22:59 UTCEPSS rescore
  14. 2026-06-12 23:11 UTCEPSS rescore
  15. 2026-06-10 22:17 UTCEPSS rescore
  16. 2026-06-08 22:07 UTCOSV refresh
  17. 2026-06-08 14:16 UTCEPSS rescore
  18. 2026-06-07 15:24 UTCEPSS rescore
  19. 2026-06-07 15:24 UTCEPSS rescore
  20. 2026-06-06 13:46 UTCEPSS rescore
  21. 2026-06-06 13:46 UTCEPSS rescore
  22. 2026-06-05 22:46 UTCEPSS rescore
  23. 2026-06-05 22:46 UTCEPSS rescore
  24. 2026-05-31 00:15 UTCEPSS rescore
  25. 2026-05-31 00:15 UTCEPSS rescore
  26. 2026-05-28 13:44 UTCEPSS rescore
  27. 2026-05-28 13:44 UTCEPSS rescore
  28. 2026-05-28 13:44 UTCEPSS rescore
  29. 2026-05-26 07:18 UTCEPSS rescore
  30. 2026-05-26 07:18 UTCEPSS rescore
  31. 2026-05-26 07:18 UTCEPSS rescore
  32. 2026-05-24 05:12 UTCEG score recompute

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 Metasploit module) (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCTechieNeurons/CVE-2024-3116_RCE_in_pgadmin_8.4
    First seen Apr 7, 2024

    Making a lab and testing the CVE-2024-3116, a Remote Code Execution in pgadmin <=8.4

    Open source ↗
  • Metasploitexploit/windows/http/pgadmin_binary_path_api✓ verified
    First seen Mar 28, 2024

    pgAdmin Binary Path API RCE

    Open source ↗

Frequently asked(5)

What is CVE-2024-3116?
CVE-2024-3116 is a high vulnerability published on April 4, 2024. pgAdmin <= 8.4 is affected by a Remote Code Execution (RCE) vulnerability through the validate binary path API. This vulnerability allows attackers to execute arbitrary code on the server hosting PGAdmin, posing a severe risk to the database management system's integrity and the security of the…
When was CVE-2024-3116 disclosed?
CVE-2024-3116 was first published in the National Vulnerability Database on April 4, 2024, with the most recent update on March 17, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-3116 actively exploited?
CVE-2024-3116 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-3116?
CVE-2024-3116 has a CVSS v3 base score of 7.4 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2024-3116?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-3116, 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-2024-3116

Explore →

Is Your Infrastructure Affected by CVE-2024-3116?

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