These pages are published after PatchSiren validates generated defensive summaries against stored public CVE and source evidence.
The CVE-2026-17566 vulnerability affects pgAdmin 4's Import/Export Data tool, allowing attackers to execute arbitrary commands via a logic bug in the _is_query_parens_balanced() checker. This critical vulnerability has a CVSS score of 9.4 and requires immediate attention. The bug incorrectly interprets backslash-escape semantics, enabling attackers to inject a TO PROGRAM clause that psql executes. The fix [truncated]
AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-07-31T16:16:59.807Z and has not been modified since then. The NVD entry is currently Received. This critical vulnerability in pgAdmin 4 arises from a discrepancy between sqlparse's string-literal lexing and PostgreSQL's parser, allowing an attacker to smuggle a COMMIT statement within a query and bypas [truncated]
The CVE-2026-17350 vulnerability affects pgAdmin 4 in SERVER mode, specifically the per-tool permission system which did not consistently enforce permission checks. This allowed authenticated users with explicit permission denials to bypass tool-level access controls. The issue was introduced in version 9.3 and fixed in version 9.17. Users should review and update their installations to mitigate this vuln [truncated]
The CVE-2026-17349 vulnerability affects pgAdmin 4, specifically the adhoc_connect_server feature introduced in version 9.0. This feature clones a server and copies sensitive information such as user_id, shared, shared_username, and stored credential fields. A non-owner can trigger an adhoc connect against another user's shared server, inheriting the source user's ownership and credentials. The fix ensure [truncated]
The pgAdmin 4 application has a vulnerability in SERVER mode, where certain routes are not properly secured with the @pga_login_required decorator, allowing unauthenticated network clients to access sensitive data and perform actions without authentication. This vulnerability affects pgAdmin 4 in SERVER mode, particularly those who have not applied the patch. The patch adds the missing @pga_login_required [truncated]
The CVE-2026-17347 vulnerability affects pgAdmin 4 versions 7.2 to 9.17, allowing an authenticated user to execute arbitrary commands as the pgAdmin service account by providing a username with shell metacharacters. This issue arises from the previous implementation of the MASTER_PASSWORD_HOOK setting, which substituted the username directly into the command string and executed the result with subprocess. [truncated]
The CVE-2026-17346 vulnerability in pgAdmin 4 arises from an incomplete fix for CVE-2026-12044, specifically in the qtLiteral hardening and template switching for COMMENT ON / pgstattuple / pgstatindex. The fix missed several sinks in test_sql_string_literal_lint.py's ALLOWLIST, including the Index Statistics query for all-indexes listing and publication and subscription dependencies.sql / get_position.sq [truncated]
CVE-2026-12050 is a SQL injection vulnerability in pgAdmin 4's named restore point endpoint. The issue allows an authenticated pgAdmin user with a connected PostgreSQL session to inject additional SQL statements. However, the injected SQL executes under the database role the user is already authenticated as, meaning the attacker gains no capability beyond what their database role already grants them.
An open redirect vulnerability was found in pgAdmin 4's multi-factor authentication flow. The MFA validate and register endpoints honored the user-supplied 'next' query/form parameter without confirming the target pointed back inside pgAdmin. This could allow an authenticated victim who clicked a link typically delivered by phishing to be sent to an attacker-controlled host directly out of the trusted auth flow.
AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-06-19T00:16:47.200Z and has not been modified since then. The NVD entry is currently Analyzed. This stored cross-site scripting vulnerability in pgAdmin 4's error-rendering and plan-node-rendering paths allows an attacker to inject arbitrary HTML, potentially leading to phishing attacks. The vulnerabil [truncated]
An HTML injection vulnerability was discovered in pgAdmin 4's cloud deployment module. The issue arises from the lack of HTML encoding in exception text from AWS, Azure, and Google SDKs, which is then rendered as HTML by the Cloud Wizard frontend. This allows an authenticated user to inject HTML, potentially leading to self-targeted attacks or, with additional cross-site request-forgery primitives, attack [truncated]
A critical vulnerability was discovered in pgAdmin 4's SQL Editor blueprint, specifically in the DELETE /sqleditor/close/<trans_id> and POST /sqleditor/initialize/sqleditor/update_connection/<sgid>/<sid>/<did> endpoints. These endpoints were missing the @pga_login_required decorator, making them accessible without authentication in server mode. This vulnerability, a missing-authentication-on-critical-func [truncated]
A critical vulnerability (CVE-2026-12045) in pgAdmin 4's AI Assistant allows an attacker with write privileges on the pgAdmin user's role to execute arbitrary SQL, potentially leading to remote code execution on the database server host. The issue arises from the AI Assistant's execute_sql_query tool, which fails to restrict multi-statement payloads, enabling an attacker to bypass read-only transactions. [truncated]
CVE-2026-12044 is a SQL injection vulnerability in pgAdmin 4, a popular administration tool for PostgreSQL databases. The vulnerability affects versions from 1.0 before 9.16 and allows an authenticated user to inject arbitrary SQL code. The issue arises from the improper handling of user-supplied description fields in various dialog templates, including Domains, Foreign Tables, Languages, and Event Trigge [truncated]
pgAdmin 4 versions prior to 9.15 contain an authentication bypass vulnerability in the account lockout mechanism. The application enforces MAX_LOGIN_ATTEMPTS only within its custom /authenticate/login view, while Flask-Security's default /login view—automatically registered and reachable on every server—fails to consult the User.locked field. This occurs because pgAdmin's User model relied on Flask-Securi [truncated]
A symbolic-link path traversal vulnerability in pgAdmin 4's File Manager allows authenticated users to write files to arbitrary locations on the server filesystem. The root cause is a mismatch between access validation and file operations: `check_access_permission` uses `os.path.abspath`, which normalizes parent-directory references but does not resolve symbolic links, while the subsequent kernel write fo [truncated]
pgAdmin 4 versions before 9.15 contain a deserialization vulnerability in the FileBackedSessionManager component. The session manager performed unsafe deserialization of session file contents using Python's standard pickle module before verifying HMAC integrity. This allowed any file placed in the sessions directory to be deserialized unconditionally. An authenticated user with write access to the session [truncated]
CVE-2026-7817 documents Local File Inclusion (LFI) and Server-Side Request Forgery (SSRF) vulnerabilities in pgAdmin 4's LLM API configuration endpoints. The issue stems from insufficient validation of user-supplied `api_key_file` and `api_url` preferences, which were passed directly to LLM provider clients without sanitization. An authenticated attacker could exploit this to read arbitrary files readable [truncated]
CVE-2026-7816 is a high-severity OS command injection vulnerability (CWE-78) in pgAdmin 4's Import/Export query export functionality, published 2026-05-11 and last modified 2026-05-26. The vulnerability exists because user-supplied input was interpolated directly into a psql `COPY` metacommand template without proper sanitization. An authenticated attacker could inject `) TO PROGRAM 'cmd'` to break out of [truncated]
A SQL injection vulnerability in pgAdmin 4's Maintenance Tool allows authenticated users with tools_maintenance permission to execute arbitrary SQL on connected PostgreSQL servers. Four JSON parameters (buffer_usage_limit, vacuum_parallel, vacuum_index_cleanup, reindex_tablespace) were concatenated directly into VACUUM/ANALYZE/REINDEX commands without proper sanitization. Attackers can break out of option [truncated]
A stored cross-site scripting (XSS) vulnerability in pgAdmin 4 allows attacker-controlled JavaScript execution via malicious PostgreSQL object names. The vulnerability exists in the Browser Tree and Explain Visualizer modules, where user-controlled object names (database, schema, table, column, etc.) were assigned to DOM elements using innerHTML. Crafted object names containing HTML markup can execute Jav [truncated]
pgAdmin 4 server mode contains multiple authorization flaws allowing authenticated users to access and modify other users' private resources. Affected modules include Server Groups, Servers, Shared Servers, Background Processes, and Debugger. The core issue is missing user-scoped filtering on object retrieval endpoints, enabling ID-guessing attacks to access private servers, server groups, background proc [truncated]
