PGADMIN4 · CVE-2025-2945 · Package
FIX → 9.2
pgAdmin 4 passes the query_commited parameter on its Query Tool download endpoint and the high_availability parameter on its cloud deploy endpoint to Python's eval(). A remote user who can send a crafted POST request can run arbitrary code on the machine running pgAdmin.
first public Apr 3, 2025 · 1 public exploit · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Any deployment of pgAdmin 4 before 9.2 is exposed, most often when pgAdmin is served as a shared web application to users on the network. Desktop-only use on a single machine with no reachable web endpoint is lower risk, but the fix is the same version bump. Deployments on managed hosting that the operator does not run are the vendor's responsibility.
Not affected if desktop-only-no-network-exposure, version-9.2-or-later
Who cares pgadmin4, postgresql, python, self-hosted
pip show pgadmin4; versions below 9.2 are affected./sqleditor/query_tool/download and /cloud/deploy endpoints are reachable from untrusted networks.Remote Code Execution security vulnerability in pgAdmin 4 (Query Tool and Cloud Deployment modules).
The vulnerability is associated with the 2 POST endpoints; /sqleditor/query_tool/download, where the query_commited parameter and /cloud/deploy endpoint, where the high_availability parameter is unsafely passed to the Python eval() function, allowing arbitrary code execution.
This issue affects pgAdmin 4: before 9.2.
This page as .md ·
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
Upgrade to 9.2
9.2 or later.GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.