Servers and applications
CVE-2026-17350
The per-tool permission system (custom roles / role-based tool permissions, introduced in pgAdmin 4 9.3) did not enforce its permission check consistently. In SERVER mode, pgAdmin 4 gates each tool behind a per-tool Flask-Security permission, but the permission decorator (permissions_required) was applied only to a single "front door" route per tool. Every other backend route and Socket.IO…
- Severity
- Medium 5.3
- Published
- 31 Jul 2026
- Last changed
- 23 Oct 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 9.17
- Exploit chance
- 0.4% in the next 30 daysHigher than 32% of CVEs. EPSS by FIRST, 19 Nov 2026
- Weakness
- Missing authorization (CWE-862)
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Read some data · Change some data
- CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X- Sources
- NVD
Description
The per-tool permission system (custom roles / role-based tool permissions, introduced in pgAdmin 4 9.3) did not enforce its permission check consistently. In SERVER mode, pgAdmin 4 gates each tool behind a per-tool Flask-Security permission, but the permission decorator (permissions_required) was applied only to a single "front door" route per tool. Every other backend route and Socket.IO handler in that tool's workflow relied solely on pga_login_required/socket_login_required, which check authentication but not the tool permission.
The reporter verified three cases against a test build: (1) a user without tools_query_tool permission received 403 on the protected sqleditor initialization route, but the same session went on to connect the server, initialize the viewdata backend chain, and retrieve real table row content; (2) a user without tools_grant_wizard received 403 on the protected acl route, but the same session still enumerated grantable objects, generated GRANT SQL, and…
Affected software
| Software | Affected versions |
|---|---|
pgAdminServers and applications · cpe:a:pgadmin:pgadmin_4 |
|
About pgAdmin
graphical administration tool for PostgreSQL
- Weekly downloads (PyPI)
- 5,570PyPI Stats, 15 Nov 2026
- Docker Hub pulls
- 455,658,756Docker Hub, 15 Nov 2026
- GitHub stars
- 3,940GitHub, 15 Nov 2026
- Forks
- 921GitHub, 15 Nov 2026
- License
- PostgreSQL LicenseWikidata
- Written in
- Python, JavaScriptWikidata
- First published on GitHub
- 20 Feb 2017GitHub
Website Source code Docker image Package
Release lines
| Release | Latest | Security fixes |
|---|---|---|
| 9 | 9.19 | Yes |
| 8 | 8.14 | Ended 6 Feb 2025 |
| 7 | 7.8 | Ended 23 Nov 2023 |
| 6 | 6.21 | Ended 13 Apr 2023 |
| 5 | 5.7 | Ended 7 Oct 2021 |
| 4 | 4.30 | Ended 25 Feb 2021 |
From endoflife.date.
Vulnerabilities in pgAdmin
- In our list
- 61
- Published in the last 12 months
- 43
- Critical, last 12 months
- 10
- High, last 12 months
- 22
- Known exploited
- 0
- CVE-2026-116252pgAdmin 4: Materialized view refresh redirects its connection through a crafted database nameHigh 7.1 30 Oct 2026
- CVE-2026-116251pgAdmin 4: A user's other sessions survive a change of their passwordLow 2.3 30 Oct 2026
- CVE-2026-116250pgAdmin 4: Files opened in a storage directory follow a symbolic link, hard link or FIFO planted after the containment checkHigh 7.3 30 Oct 2026
- CVE-2026-116249pgAdmin 4: Connection file paths and parameter keys escape the user's storage directoryHigh 7.2 30 Oct 2026
- CVE-2026-116248pgAdmin 4: Non-administrators can share a server with every userMedium 6.0 30 Oct 2026
- CVE-2026-116247pgAdmin 4: libpq uses the pgAdmin service account's own password file and client certificateHigh 7.1 30 Oct 2026