PGADMIN4 · CVE-2025-13780 · Package
FIX → 9.11
pgAdmin's filter for dangerous psql meta-commands during restore misses SQL files that start with a UTF-8 byte order mark. An attacker who supplies such a file can get psql to run a shell command through a meta-command such as \! during a restore.
first public Dec 11, 2025 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams running pgAdmin 4 in a server or desktop-hosted setup where users can restore SQL files through the PLAIN restore feature. Installations that never restore user-supplied SQL files are less exposed. The sources do not say whether managed hosting changes exposure.
Not affected if no-sql-restore, pgadmin-9.11-or-later
Who cares pgadmin4, postgresql, python, self-hosted
pip show pgadmin4 and compare against 9.11.Upgrade to 9.11
pgadmin4 9.11 (fixed version per the product range; affected below )The PLAIN restore meta-command filter introduced in pgAdmin as part of the fix for CVE-2025-12762 does not detect meta-commands when a SQL file begins with a UTF-8 Byte Order Mark (EF BB BF) or other special byte sequences. The implemented filter uses the function has_meta_commands(), which scans raw bytes using a regular expression. The regex does not treat the bytes as ignorable, so meta-commands such as \\! remain undetected. When pgAdmin invokes psql with --file, psql strips the bytes and executes the command. This can result in remote command execution during a restore operation.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
9.11GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.