Loading story…
The pgAdmin Development Team released pgAdmin 4 v9.15 to fix multiple high-impact vulnerabilities affecting server-mode and web deployments, including CVE-2026-7813, CVE-2026-7815, and CVE-2026-7816. The most severe issues allowed authenticated users to cross tenant boundaries and access other users’ private objects by enumerating sequential IDs, expose sensitive connection details, and in some shared-server cases modify passexec_cmd so arbitrary shell commands would run when the legitimate owner next connected. PostgreSQL said the release also addresses stored XSS, local file inclusion and SSRF, unsafe deserialization that could lead to remote code execution, symlink-based path traversal, and an account-lockout bypass.
Two additional flaws enabled authenticated users to reach operating system command execution through pgAdmin’s integration with PostgreSQL tooling. CVE-2026-7815 affected the Maintenance Tool, where unsafe concatenation of JSON-controlled fields into SQL for VACUUM, ANALYZE, and REINDEX could be abused and, with a superuser-connected PostgreSQL role, escalated via PostgreSQL features into command execution on the database host. CVE-2026-7816 affected the Import/Export query export feature, where unsanitized input in the underlying psql \copy metacommand could let attackers execute commands on the pgAdmin server or write arbitrary files. Version 9.15 introduces structural authorization checks, input allow lists, safer identifier handling, session-file encryption with Fernet, stricter file permissions, and a move from SHA-1 to SHA-256 for the default session digest.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
1 event from the most recent confirmed update back to the earliest known activity.
The pgAdmin Development Team announced pgAdmin 4 version 9.15 on 2026-05-11. The release fixed multiple vulnerabilities, including CVE-2026-7813, CVE-2026-7815, and CVE-2026-7816, along with other issues such as stored XSS, SSRF, unsafe deserialization, path traversal, and an account-lockout bypass.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
9 references tracked. Mallory keeps watching after this page renders.
cve.org
Open sourcezeropath.com
Open sourcezeropath.com
Open sourcepostgresql.org
Open sourcepgadmin.org
Open sourcecve.org
Open sourcezeropath.com
Open sourcegithub.com
Open sourcegithub.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
pgAdmin 4 developers released security updates for two critical vulnerabilities affecting versions earlier than **9.2**, including **CVE-2025-2945** and **CVE-2025-2946**. The most severe issue, **CVE-2025-2945** (`CVSS 9.9`), is a remote code execution flaw in the **Query Tool** and **Cloud Deployment** components caused by unsafe use of Python `eval()` on unsanitized POST parameters, allowing an authenticated remote attacker to compromise confidentiality, integrity, and availability. The second flaw, **CVE-2025-2946** (`CVSS 9.1`), is a cross-site scripting vulnerability in the **Query Tool** and **View/Edit Data** components that can execute attacker-controlled HTML or JavaScript when query results are rendered in the result grid. Public proof-of-concept exploit code is available for the vulnerabilities, increasing exploitation risk, and users are being urged to upgrade **pgAdmin 4** to **version 9.2 or later** immediately.
Jul 24, 2026
A critical remote code execution vulnerability, tracked as CVE-2025-13780, was discovered in *pgAdmin 4*, the widely used open-source PostgreSQL database management tool. The flaw allows attackers to bypass security filters in the plain-text restore feature by inserting unexpected whitespace characters, enabling the execution of arbitrary shell commands on the host server through maliciously crafted SQL dump files. The vulnerability affects pgAdmin 4 versions prior to 9.11 and was found to stem from an inadequate regular expression filter that failed to block dangerous commands effectively. Security researchers at EndorLabs identified the issue and reported that attackers could exploit this weakness to gain unauthorized access and potentially take over affected servers. In response, the pgAdmin development team released version 9.11, which implements the `\restrict` command to disable hazardous operations during the restore process, fundamentally improving the security model by enforcing restrictions at the execution level rather than relying solely on input filtering. Users are strongly advised to update to the latest version to mitigate the risk of exploitation.
Jun 29, 2026
A **critical SQL injection flaw** tracked as `CVE-2026-17351` affects pgAdmin 4 and allows an authenticated remote attacker to induce the product's AI Assistant to bypass intended read-only database protections. The bug is an incomplete fix for `CVE-2026-12045` and arises from a parsing mismatch: pgAdmin validates LLM-generated SQL with `sqlparse`, while PostgreSQL interprets the same input differently, enabling a crafted payload to be seen as a single statement during validation but executed as multiple statements by the database. Public reporting says the issue affects pgAdmin 4 releases before `9.18`, including versions `9.13` through `9.16`, and a public proof of concept is reportedly available. By smuggling a `COMMIT` into the SQL stream, an attacker can escape the read-only transaction wrapper and regain write capability, potentially leading to unauthorized SQL execution, data modification, privilege escalation, security control bypass, and in some environments a return of arbitrary code execution risk through the same indirect prompt-injection path as the earlier bug. Researchers reported that a proposed mitigation using psycopg3 prepared execution failed under default pgAdmin settings because `prepare_threshold` remained unset, causing fallback to PostgreSQL's simple query protocol; the corrected fix forces `conn.prepare_threshold = 0` on the dedicated read-only connection so PostgreSQL rejects multi-statement input via the extended query protocol. Authorities recommend upgrading to the latest vendor patches immediately.
Aug 3, 2026