How many CVEs have patched _execute_readonly_query?

1 published CVEs changed _execute_readonly_query in pgadmin-org/pgadmin4, in 1 distinct patches totalling 6 changed lines, between 2026 and 2026.

What is the latest CVE that changed _execute_readonly_query?

CVE-2026-17351 (pgAdmin 4: AI Assistant read-only transaction bypass via sqlparse/PostgreSQL lexer disagreement (incomplete fix for CVE-2026-12045)), published 2026-07-31, changed lines 329 to 332 of web/pgadmin/llm/tools/database.py.

How does _execute_readonly_query compare to the rest of pgadmin-org/pgadmin4?

pgadmin-org/pgadmin4 has 31 CVEs with a located fix in total; 1 of them changed _execute_readonly_query.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

pgadmin-org/pgadmin4

Function

_execute_readonly_query

Name: _execute_readonly_query in pgadmin-org/pgadmin4: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

web/pgadmin/llm/tools/database.py

Last patched July 31, 2026

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

6

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

_execute_readonly_query in pgadmin-org/pgadmin4 was changed by 1 published CVE fixes in 2026, in 1 distinct patches that added or removed 6 lines in total.

pgadmin-org/pgadmin4 has 31 CVEs with a located fix in total, so 3% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed _execute_readonly_query, newest first, with the lines each fix touched.

pgAdmin 4: AI Assistant read-only transaction bypass via sqlparse/PostgreSQL lexer disagreement (incomplete fix for CVE-2026-12045)
CVE-2026-17351 · lines 329–332 · +4 −2
Critical · CVSS 9.4
EPSS 0.5%2026-07-31

Get an alert when the next CVE fix lands in pgadmin-org/pgadmin4, with the patched functions.

Monitor pgadmin4 CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in pgadmin-org/pgadmin4 changed by the most CVE fixes.

create_import_export_job4 CVEs · web/pgadmin/tools/import_export/__init__.py connect_database3 CVEs · web/pgadmin/tools/schema_diff/__init__.py adhoc_connect_server3 CVEs · web/pgadmin/misc/workspaces/__init__.py set_arguments_sqlite3 CVEs · web/pgadmin/tools/debugger/__init__.py panel3 CVEs · web/pgadmin/tools/erd/__init__.py connect_server3 CVEs · web/pgadmin/tools/schema_diff/__init__.py

All patched functions in pgadmin-org/pgadmin4

Frequently asked questions

Common questions about CVE fixes to _execute_readonly_query.

How many CVEs have patched _execute_readonly_query?: 1 published CVEs changed _execute_readonly_query in pgadmin-org/pgadmin4, in 1 distinct patches totalling 6 changed lines, between 2026 and 2026.
What is the latest CVE that changed _execute_readonly_query?: CVE-2026-17351 (pgAdmin 4: AI Assistant read-only transaction bypass via sqlparse/PostgreSQL lexer disagreement (incomplete fix for CVE-2026-12045)), published 2026-07-31, changed lines 329 to 332 of web/pgadmin/llm/tools/database.py.
How does _execute_readonly_query compare to the rest of pgadmin-org/pgadmin4?: pgadmin-org/pgadmin4 has 31 CVEs with a located fix in total; 1 of them changed _execute_readonly_query.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track pgadmin-org/pgadmin4 CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing