CVE-2024-3116 — Remote Code Execution Vulnerability through the validate binary path API in pgAdmin 4

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.

Published Apr 4, 2024Updated Mar 14, 2025Sources: cvelistV5, PostgreSQL

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

65%

chance of exploitation in 30 days

Affects

pgadmin org

pgadmin_4

CVSS base

7.4

HIGH

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

PoC

none · proof-of-concept · active

Automatable

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (2)

pgadmin org postgresql

Products (1)

pgadmin 4

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
7.4	CVSS 3.1	HIGH	—	—	cvelistV5

Weakness & attack patterns

CWE-77

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Indexed by

metasploitpoc in github

References

4 on the record

Elsewhere on this site

pgadmin orgevery CVE for this vendor
postgresqlevery CVE for this vendor
CWE-77other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.