Skip to content
Fencer Intel
critical 9.9

CVE-2025-2945 in the critical feed json

pgAdmin 4: Remote Code Execution in Query Tool and Cloud Deployment

published last yr. modified 4mo ago also EUVD-2025-9605 , GHSA-g73c-fw68-pwx3 , PYSEC-2026-451

cvss
9.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
56.3%
EPSS 56.3% chance of exploitation in 30 days, percentile 99%
public exploits
1
Metasploit

Summary

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.

Patch / fix

  • pypi pgadmin4 9.2
  • pgadmin.org pgAdmin 4 9.2
  • pgadmin4 openSUSE Tumbleweed 9.2-1.1

opensuse advisories openSUSE-SU-2025:14983-1

Is CVE-2025-2945 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-2945 updated cvss 9.9

pgadmin: pgAdmin 4: Remote Code Execution in Query Tool and Cloud Deployment

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. First public exploit (Metasploit exploit/multi/http/pgadmin_query_tool_authenticated)
  2. Published

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

56.30% chance of exploitation in the next 30 days, higher than 99% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

CVSS scores

assigned by version score vector
CNA 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
GitHub 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
OSV 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi pgadmin4
<9.2
9.2

Affected products

  • pgadmin.org pgAdmin 4

Classification

Weakness
  • CWE-94 Improper Control of Generation of Code

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.