Servers and applications
CVE-2026-86863
pgAdmin 4's Webserver authentication source is intended to accept an identity asserted by the web server or reverse proxy in front of pgAdmin, delivered through the WSGI/CGI environment. WebserverAuthentication.get_user() read config.WEBSERVER_REMOTE_USER from request.environ and, when that returned nothing, fell back to reading the same name directly from the inbound HTTP request headers via…
- Severity
- Critical 9.3
- Published
- 17 Sept 2026
- Last changed
- 21 Sept 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 9.18
- Exploit chance
- 0.6% in the next 30 daysHigher than 48% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · No login needed · No user action needed
- Attacker can
- Read data · Change data · Take it down
- CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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
pgAdmin 4's Webserver authentication source is intended to accept an identity asserted by the web server or reverse proxy in front of pgAdmin, delivered through the WSGI/CGI environment. WebserverAuthentication.get_user() read config.WEBSERVER_REMOTE_USER from request.environ and, when that returned nothing, fell back to reading the same name directly from the inbound HTTP request headers via request.headers.get(). An inbound HTTP header is written by whoever sends the request, so any client able to reach pgAdmin could supply that header itself and be authenticated as any username it named, including an existing Administrator, without presenting a password or any other credential. The environment lookup could also be satisfied by a client-supplied header whenever WEBSERVER_REMOTE_USER was configured to an HTTP_-prefixed or hyphenated name such as HTTP_X_FORWARDED_USER or X-Forwarded-User, since WSGI servers place inbound headers into the environment under exactly those names.
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