# SQL injection vulnerability in pgAdmin 4 Maintenance Tool

Advisory record · `GHSA-hp84-p2gq-6fvr`

- **Identifiers:** `GHSA-hp84-p2gq-6fvr` · `CVE-2026-7815` · `PYSEC-2026-2867`
- **State:** Confirmed
- **Severity:** CVSS 8.7 High
- **Critical:** No
- **Weakness (CWE):** [CWE-89](https://cwe.mitre.org/data/definitions/89.html)
- **Tags:** [SQL injection](https://agentprime.io/advisories/tag/sql-injection.md)
- **Published:** 11 May 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 11 May 2026, 18:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `pgadmin4` (PyPI): affected `<9.15`; fixed in `9.15`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> pgAdmin 4 versions before 9.15 are vulnerable to SQL injection in the Maintenance Tool, where four user-supplied JSON fields were concatenated directly into VACUUM, ANALYZE, and REINDEX commands. An authenticated user with the tools_maintenance permission could execute arbitrary SQL on the connected PostgreSQL server, and potentially run operating-system commands on the database host. Upgrade to pgAdmin 4 version 9.15 or later, which adds server-side allow-listing of the affected fields.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.7 High, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`, from CNA (PostgreSQL)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0046, the 40th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:11 UTC: First seen by agentprime
- 31 Oct 2026, 14:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-hp84-p2gq-6fvr)

## Sources

- [GitHub Advisory Database: GHSA-hp84-p2gq-6fvr](https://github.com/advisories/GHSA-hp84-p2gq-6fvr)
- [OSV: GHSA-hp84-p2gq-6fvr](https://osv.dev/vulnerability/GHSA-hp84-p2gq-6fvr)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-7815>
- <https://github.com/pgadmin-org/pgadmin4/issues/9898>
- <https://github.com/pgadmin-org/pgadmin4/commit/cf53953d9>
- <https://github.com/pgadmin-org/pgadmin4>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-hp84-p2gq-6fvr>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-hp84-p2gq-6fvr/>. Everything for agents: <https://agentprime.io/llms.txt>.