pgAdmin 4 - Authentication Bypass

pgAdmin 4 versions 8.11 and earlier are vulnerable to a security flaw in OAuth2 authentication. This vulnerability allows an attacker to potentially obtain the client ID and secret, leading to unauthorized access to user data. id: CVE-2024-9014 info: name: pgAdmin 4 - Authentication Bypass author...

pgAdmin < 6.17 - Unauthenticated Remote Code Execution

pgAdmin prior to 6.17 contains an insecure HTTP API caused by improper access control, letting unauthenticated users execute arbitrary external utilities via path manipulation, exploit requires no authentication. id: CVE-2022-4223 info: name: pgAdmin 6.17 - Unauthenticated Remote Code Execution...

CVE-2026-17350

A flaw was found in pgAdmin 4. In SERVER mode, an authenticated user who has been explicitly denied access to a specific tool by an administrator could still bypass this restriction. This is due to inconsistent enforcement of the per-tool permission system, where backend routes and Socket.IO...

CVE-2026-17349

A flaw was found in pgAdmin 4. An authenticated, low-privilege user could exploit a vulnerability in the adhoc server cloning feature to gain unauthorized access to another user's stored database credentials. By initiating an adhoc connection to a shared server owned by another user, the cloning...

pgadmin4-9.17-1.1 on GA media (moderate)

pgadmin4-9.17-1.1 on GA media Announcement ID: openSUSE-SU-2026:11508-1 Rating: moderate Cross-References: CVE-2026-12044 CVE-2026-12045 CVE-2026-12046 CVE-2026-12047 CVE-2026-12048 CVE-2026-12049 CVE-2026-12050 CVE-2026-1707 CVE-2026-17347 CVE-2026-17349 CVE-2026-17350 CVE-2026-17351...

CVE-2026-17346

A flaw was found in pgAdmin 4. A low-privileged user can exploit a SQL injection vulnerability when object names, such as schema, table, publication, or subscription names, containing special characters are not properly escaped. When any user, including those with higher privileges, views the...

Exploit for Code Injection in Pgadmin Pgadmin_4

No d...

CVE-2026-17347

A flaw was found in pgAdmin 4. The MASTERPASSWORDHOOK setting, which allows administrators to configure an external command for per-user encryption keys, improperly substitutes usernames into the command string. An authenticated user can exploit this by providing a specially crafted username...

CVE-2026-17351

A flaw was found in pgAdmin 4. The AI Assistant's SQL query tool, designed for read-only operations, contains a vulnerability where a disagreement between its SQL validator and the PostgreSQL database parser allows for a transaction bypass. A remote attacker with low-privilege database write acce...

CVE-2026-17566

A flaw was found in pgAdmin 4, a management tool for PostgreSQL databases. The Import/Export Data feature incorrectly processes certain user-provided SQL queries, specifically regarding how backslash characters are interpreted. This vulnerability allows an authenticated remote attacker, with...

CVE-2026-17348

A flaw was found in pgAdmin 4. In SERVER mode, an unauthenticated network client could exploit missing authentication controls on specific routes. This vulnerability allows an attacker to enumerate constraint metadata, read sensitive preference values, delete table constraints, and force-close...

Exploit for CVE-2026-17351

CVE-2026-17351 — pgAdmin 4 AI Assistant Read-Only Bypass via L...

CVE-2026-17347

The MASTERPASSWORDHOOK setting, introduced in pgAdmin 4 7.2, lets an administrator configure an external command that returns a per-user encryption key, with %u in the configured string replaced by the current user's name. The previous implementation substituted the username directly into the...

CVE-2026-17346

The fix for CVE-2026-12044 in pgAdmin 4 9.16 hardened qtLiteral and switched sixteen COMMENT ON / pgstattuple / pgstatindex templates to it, but missed several sinks that had been placed in testsqlstringliterallint.py's ALLOWLIST on the incorrect assumption that schema, table, publication, and...

CVE-2026-17566 pgAdmin 4: RCE via backslash-escape mismatch in Import/Export Data query guard (incomplete defense, sibling gap to CVE-2025-13780)

pgAdmin 4's Import/Export Data tool builds a psql \copy ... command line by interpolating a user-supplied SQL query into a Jinja template and passing the rendered line to psql via --command. To stop an attacker from breaking out of the ... wrapper, createimportexportjob route POST...

CVE-2026-17566 pgAdmin 4: RCE via backslash-escape mismatch in Import/Export Data query guard (incomplete defense, sibling gap to CVE-2025-13780)

pgAdmin 4's Import/Export Data tool builds a psql \copy ... command line by interpolating a user-supplied SQL query into a Jinja template and passing the rendered line to psql via --command. To stop an attacker from breaking out of the ... wrapper, createimportexportjob route POST...

CVE-2026-17566 pgAdmin 4: RCE via backslash-escape mismatch in Import/Export Data query guard (incomplete defense, sibling gap to CVE-2025-13780)

pgAdmin 4's Import/Export Data tool builds a psql \copy ... command line by interpolating a user-supplied SQL query into a Jinja template and passing the rendered line to psql via --command. To stop an attacker from breaking out of the ... wrapper, createimportexportjob route POST...

CVE-2026-17566

Summary of CVE-2026-17566 (pgAdmin 4): The Import/Export Data tool builds a psql \copy (...) command by interpolating a user-supplied SQL query into a Jinja template and passing it via --command. A flawed parenthesis-balance check in create_import_export_job() treated a backslash-quote (') as esc...

EUVD-2026-51565

pgAdmin 4's Import/Export Data tool builds a psql \copy ... command line by interpolating a user-supplied SQL query into a Jinja template and passing the rendered line to psql via --command. To stop an attacker from breaking out of the ... wrapper, createimportexportjob route POST...

CVE-2026-17351 pgAdmin 4: AI Assistant read-only transaction bypass via sqlparse/PostgreSQL lexer disagreement (incomplete fix for CVE-2026-12045)

The fix for CVE-2026-12045 in pgAdmin 4 9.16 required the LLM-supplied query passed to the AI Assistant's executesqlquery tool to parse, via sqlparse, as exactly one non-transaction-control statement before running it inside a BEGIN TRANSACTION READ ONLY wrapper. sqlparse's string-literal lexing...