SQL Injection in pgAdmin 4 Maintenance Tool Parameters

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.

Casky was already ahead

This CVE exploits attack patterns that Casky's 301matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

pgAdmin 4's maintenance tool contains a critical SQL injection vulnerability (CVSS 8.8) where four JSON input fields—buffer_usage_limit, vacuum_parallel, vacuum_index_cleanup, and reindex_tablespace—are concatenated directly into VACUUM, ANALYZE, and REINDEX commands without sanitization. An authenticated user with tools_maintenance permissions can break out of the intended option syntax and execute arbitrary SQL commands against the connected PostgreSQL server. The risk escalates significantly because injected SQL can invoke COPY...TO PROGRAM to achieve operating system command execution, allowing complete database and potentially system compromise. This affects any organization running pgAdmin 4 with user accounts possessing maintenance tool access.

Casky's 301 mapped skills leverage Claude's extended reasoning to detect the attack chain across MITRE ATT&CK's Initial Access (TA0001) and Persistence (TA0043) techniques. Practitioners using Casky would identify execution flows showing: authenticated SQL injection payloads injected through maintenance tool parameters, SQL command concatenation patterns without prepared statements, privilege escalation from database user context to OS execution via COPY...TO PROGRAM, and post-exploitation persistence mechanisms. The platform's skill correlation reveals how this CWE-89 SQL injection becomes a stepping stone for lateral movement and credential harvesting within PostgreSQL environments, enabling security teams to trace the complete attack narrative and implement detection rules across database activity logs, authentication systems, and command execution monitoring.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

301 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-7815.

analyzing-apt-group-with-mitre-navigator

threat intelligence · low

Run

analyzing-campaign-attribution-evidence

threat intelligence · low

Run

analyzing-certificate-transparency-for-phishing

threat intelligence · low

Run

MITRE ATT&CK Techniques

TA0001 TA0043

Investigate the attack patterns behind CVE-2026-7815

Casky has 301 skills that investigate the attack patterns behind CVE-2026-7815. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn