Quick answers
- Is CVE-2024-3116 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2024-3116 being exploited in the wild.
- How severe is CVE-2024-3116?
- Low severity, with a CVSS score of 3.1, published 7 July 2026.
- Which products and versions are affected?
- pgAdmin <= 8.4 (fixed in 8.5); pgadmin4 (PyPI) ECOSYSTEM:introduced=0,fixed=8.5.
- Is there a fix for CVE-2024-3116?
- Yes. pgadmin4 (PyPI): upgrade to 8.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2024-3116 attacked?
- It is attacked over the network.
- Am I affected by CVE-2024-3116?
- Check whether you run pgAdmin or pgadmin4 (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- pgadmin4 (PyPI): upgrade to 8.5 or later
pip install "pgadmin4>=8.5"
Technical details
pgAdmin versions through 8.4 contain a Remote Code Execution vulnerability in the validate binary path API endpoint. The vulnerability is a command injection issue (CWE-77) where user-supplied input is not properly sanitized before being passed to system commands. An authenticated user can exploit this by crafting a malicious payload in the binary path validation parameter to execute arbitrary operating system commands. The vulnerability requires authentication to trigger but allows an authenticated user to execute code with the privileges of the pgAdmin server process. A patch was released in pgAdmin 8.5.
Affected products
- pgAdmin pgAdmin <= 8.4 (fixed in 8.5)
Identifiers
- CVE-2024-3116
- GHSA-27jx-ffw8-xrqv
- PYSEC-2026-1767
Timeline
- 2024-03-28: disclosed: Vulnerability reported on GitHub
- 2024-04-04: advisory: Security advisory published
- 2024-04-04: patched: Patch released in version 8.5