Skip to main content
VulnerabilityPublished

CVE-2026-7815: pgAdmin 4 · SQL Injection

Affects pgAdmin 4Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 9.15 soon.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 9.15
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade pgAdmin 4 to 9.15.

Affected software

ProductAffectedFixed in
pgadmin.orgpgAdmin 4Affected
  • >=7.6 <9.15
Fixed in–
GitHubpgadmin-org/pgadmin4pkg:github/pgadmin-org/pgadmin4Other threatsAffected
  • <=9.14
  • =7.6
Fixed in–
GitHubpgAdmin 4pkg:github/pgAdmin 4Other threatsAffected
  • >=7.6 <9.15
Fixed in
  • 9.15

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The vendor has indicated that the fix is included in pgAdmin 4 version 9.15, which introduces server-side allow-listing and safer quoting to prevent injection. Until patched, restrict access to users with tools_maintenance permission and monitor for suspicious activity related to maintenance commands.

Description

SQL injection vulnerability in pgAdmin 4 Maintenance Tool. Four user-supplied JSON fields (buffer_usage_limit, vacuum_parallel, vacuum_index_cleanup, reindex_tablespace) were concatenated directly into the rendered VACUUM/ANALYZE/REINDEX command and passed to psql --command. An authenticated user with the tools_maintenance permission could break out of the option syntax and execute arbitrary SQL on the connected PostgreSQL server. The injected SQL could in turn invoke COPY ... TO PROGRAM to escalate to operating-system command execution on the database host. Fix introduces server-side allow-listing of all four fields and switches reindex_tablespace from manual quoting to the qtIdent filter. This issue affects pgAdmin 4: before 9.15.

References

Community reviews

Loading reviews…