Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-86863 – Authentication Bypass – pgAdmin 4 versions 6.2 through 9.17

Be the first to know when new zero-days emerge:

Summary

CVE-2026-86863 is a critical authentication bypass vulnerability (CWE-290: Authentication Bypass by Spoofing) in pgAdmin 4’s "Webserver" authentication mode. When this mode is enabled, an unauthenticated network attacker can supply a client-controlled HTTP header to be logged in as an arbitrary user, including an administrator, without presenting any credentials. The flaw carries a CVSS v3.1 base score of 9.8 (Critical).

Technical details

  • Root cause: pgAdmin’s WebserverAuthentication.get_user() reads the configured WEBSERVER_REMOTE_USER identity from the WSGI/CGI environment; when that variable is absent it falls back to reading the same name directly from the inbound HTTP request headers via request.headers.get().
  • Because HTTP request headers are set by whoever sends the request, any client able to reach the pgAdmin instance could supply that header itself and assert any username, including an existing administrator account.
  • The exposure is widened further when WEBSERVER_REMOTE_USER is configured to an HTTP_-prefixed or hyphenated name (e.g., HTTP_X_FORWARDED_USER), since WSGI’s convention of converting HTTP headers into HTTP_-prefixed environment variables lets a client-supplied header satisfy the same environment lookup.
  • Attack vector: network, no authentication or user interaction required (AV:N/AC:L/PR:N/UI:N).
  • Impact: complete compromise of the pgAdmin installation, including full administrative access and exposure of all stored database connection credentials.
  • Trigger condition: the "webserver" authentication source must be enabled in AUTHENTICATION_SOURCES (i.e., pgAdmin deployed in server mode behind a reverse proxy/web server intended to assert user identity).

Affected software

  • pgAdmin 4 versions 6.2 up to (but not including) 9.18, when the "webserver" authentication source is enabled.

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade to pgAdmin 4 version 9.18 or later, which introduces a stricter, opt-in trust model — genuine WSGI-provided identity is distinguished from header-derived identity, header-based identity assertion requires explicit opt-in via WEBSERVER_REMOTE_USER_FROM_HEADER, the requesting peer must be listed in WEBSERVER_TRUSTED_PROXIES, an optional shared secret (WEBSERVER_SHARED_SECRET_HEADER/WEBSERVER_SHARED_SECRET) can be enforced via constant-time comparison, and login is refused for accounts whose auth source is not webserver.
  • If immediate patching is not possible: Disable "webserver" authentication mode until upgraded, or ensure the reverse proxy in front of pgAdmin strips/overwrites any client-supplied identity headers (e.g., X-Forwarded-User or whatever header maps to WEBSERVER_REMOTE_USER) before forwarding requests, and restrict direct network access to the pgAdmin backend so it is only reachable through the trusted proxy.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge