pgAdmin 4: AI Assistant read-only transaction bypass allows unauthorised writes and remote code execution
Read-only transaction bypass in the pgAdmin 4 AI Assistant allows an attacker who can influence database content that the assistant reads to execute arbitrary SQL with the privileges of the pgAdmin user's database role. The AI Assistant's execute_sql_query tool runs LLM-generated SQL inside a BEGIN TRANSACTION READ ONLY wrapper to prevent data modification. The LLM-supplied query was forwarded to the database driver without restriction to a single statement or to read-only verbs, so a multi-statement payload beginning with COMMIT, END, ROLLBACK, or ABORT terminated the read-only transaction and ran subsequent statements in autocommit mode. The trailing ROLLBACK then had no effect. Delivery is via prompt injection: an attacker who can write content into any object the AI Assistant may inspect (a row, a column value, a comment) can cause the LLM to emit the multi-statement payload as a tool call. With ordinary write privileges on the pgAdmin user's role the attacker can perform unauthorised data modification. When the pgAdmin user's role is a PostgreSQL superuser or holds pg_execute_server_program, the chain extends to remote code execution on the database server host via COPY ... TO PROGRAM. Fix validates the LLM-supplied query up front: it must parse to exactly one non-empty / non-comment statement whose leading real token (after stripping whitespace, comments, and punctuation) is one of SELECT, WITH, EXPLAIN, SHOW, VALUES, or TABLE. Transaction-control verbs, DML, DDL, CALL,
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-12045
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 06:28 UTC · Revision 1
Source evidence
pgAdmin 4: AI Assistant read-only transaction bypass allows unauthorised writes and remote code execution
core-osv · Original sourcePublished 18 Jun 2026, 23:37 UTC
Read-only transaction bypass in the pgAdmin 4 AI Assistant allows an attacker who can influence database content that the assistant reads to execute arbitrary SQL with the privileges of the pgAdmin user's database role. The AI Assistant's execute_sql_query tool runs LLM-generated SQL inside a BEGIN TRANSACTION READ ONLY wrapper to prevent data modification. The LLM-supplied query was forwarded to the database driver without restriction to a single statement or to read-only verbs, so a multi-statement payload beginning with COMMIT, END, ROLLBACK, or ABORT terminated the read-only transaction and ran subsequent statements in autocommit mode. The trailing ROLLBACK then had no effect. Delivery is via prompt injection: an attacker who can write content into any object the AI Assistant may inspect (a row, a column value, a comment) can cause the LLM to emit the multi-statement payload as a tool call. With ordinary write privileges on the pgAdmin user's role the attacker can perform unauthorised data modification. When the pgAdmin user's role is a PostgreSQL superuser or holds pg_execute_server_program, the chain extends to remote code execution on the database server host via COPY ... TO PROGRAM. Fix validates the LLM-supplied query up front: it must parse to exactly one non-empty / non-comment statement whose leading real token (after stripping whitespace, comments, and punctuation) is one of SELECT, WITH, EXPLAIN, SHOW, VALUES, or TABLE. Transaction-control verbs, DML, DDL, CALL,
osv:CVE-2026-12045
Complete source record
{
"id": "1b36e9ff8698ceb598b79a31b2a4efc4c3585e2ea3b47cf7ddf75c6040fb283f",
"url": "https://osv.dev/vulnerability/CVE-2026-12045",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "pgAdmin 4: AI Assistant read-only transaction bypass allows unauthorised writes and remote code execution",
"summary": "Read-only transaction bypass in the pgAdmin 4 AI Assistant allows an attacker who can influence database content that the assistant reads to execute arbitrary SQL with the privileges of the pgAdmin user's database role. The AI Assistant's execute_sql_query tool runs LLM-generated SQL inside a BEGIN TRANSACTION READ ONLY wrapper to prevent data modification. The LLM-supplied query was forwarded to the database driver without restriction to a single statement or to read-only verbs, so a multi-statement payload beginning with COMMIT, END, ROLLBACK, or ABORT terminated the read-only transaction and ran subsequent statements in autocommit mode. The trailing ROLLBACK then had no effect. Delivery is via prompt injection: an attacker who can write content into any object the AI Assistant may inspect (a row, a column value, a comment) can cause the LLM to emit the multi-statement payload as a tool call. With ordinary write privileges on the pgAdmin user's role the attacker can perform unauthorised data modification. When the pgAdmin user's role is a PostgreSQL superuser or holds pg_execute_server_program, the chain extends to remote code execution on the database server host via COPY ... TO PROGRAM. Fix validates the LLM-supplied query up front: it must parse to exactly one non-empty / non-comment statement whose leading real token (after stripping whitespace, comments, and punctuation) is one of SELECT, WITH, EXPLAIN, SHOW, VALUES, or TABLE. Transaction-control verbs, DML, DDL, CALL,",
"evidence": "osv:CVE-2026-12045",
"products": [],
"severity": "critical",
"structured": {
"id": "CVE-2026-12045",
"aliases": [
"CVE-2026-12045"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/pgadmin-org/pgadmin4",
"type": "GIT",
"events": [
{
"introduced": "5b231ddd3f7aca5d6e7c03c21e7e1bc94b8c3b03"
},
{
"fixed": "888a053231923e6704b56165cf248db056252144"
},
{
"fixed": "bf4792444446f0e7ab721d23cbd6bfe6afaa7a8b"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:pgadmin:pgadmin_4:*:*:*:*:*:postgresql:*:*",
"range": [
{
"introduced": "9.13"
},
{
"fixed": "9.16"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "bf4792444446f0e7ab721d23cbd6bfe6afaa7a8b"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"versions": [
"REL-9_15",
"REL-9_14",
"REL-9_13"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-12045.json"
}
}
],
"modified": "2026-10-28T02:30:26.365117236Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/12xxx/CVE-2026-12045.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-12045",
"https://github.com/pgadmin-org/pgadmin4/issues/10022",
"https://github.com/pgadmin-org/pgadmin4/commit/bf4792444446f0e7ab721d23cbd6bfe6afaa7a8b",
"https://github.com/pgadmin-org/pgadmin4"
],
"provider_metadata": {
"cwe_ids": [
"CWE-77",
"CWE-89"
],
"cna_assigner": "PostgreSQL",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/12xxx/CVE-2026-12045.json"
}
},
"related_cves": [
{
"value": "CVE-2026-12045",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 493054,
"published_at": "2026-06-18T23:37:35.182+00:00"
}