CVE-2026-116248: pgAdmin 4: Non-administrators can share a server with every user

Published Oct 30, 2026

Updated

In pgAdmin 4 server mode only administrators are meant to share a server with all users; the server dialog shows the Shared switch only to them. The create and update endpoints of the server API, however, stored the "shared" flag and shared username they were sent, so any user able to register a server could share one with every other user. The servers.json import had a similar gap: a non-administrator's "Shared" entries were removed only after validation, so a file that also held an invalid entry could create a shared server.

A shared server carries no credentials, so this gives no direct access. It lets a user plant a server, named to look trusted, in every other user's tree and pointing at a host the user controls; anyone who then connects to it presents their own database password to that host.

The fix refuses a non-administrator's request that would share a server with HTTP 403, prunes a non-administrator's shared entries from a servers.json import before validating it, and warns at startup about servers shared earlier by non-administrators.

This issue affects pgAdmin 4: before 9.19.

Event History

Oct 30, 2026

CVE Published

via MITRE·07:55 PM

Data Sourced

via MITRE·07:55 PM

DescriptionSeverityWeakness

Data Sourced

via NVD·08:17 PM

DescriptionSeverityWeakness

Frequently Asked Questions

Who can exploit this issue?

Any non-administrator who is allowed to register a server in pgAdmin 4 server mode can exploit it. Exploitation requires sending create or update API requests with sharing fields, or using a crafted servers.json import that includes shared entries alongside an invalid entry.

What must happen for credentials to be exposed?

The attacker cannot obtain credentials directly from the shared server entry because shared servers carry no credentials. Another user must see the attacker-controlled shared server and connect to it, at which point that user may submit their own database password to the attacker-controlled host.

Are default deployments affected?

The issue applies to pgAdmin 4 running in server mode where non-administrators can register servers. It affects versions before 9.19.

What can be done before upgrading?

Limit server-registration and servers.json import capabilities to trusted users, and review shared server entries for ones created by non-administrators or pointing to untrusted hosts. Users should avoid connecting to unexpected shared servers, particularly entries with trusted-looking names.

How can administrators identify possible prior abuse?

The fixed version warns at startup about servers that were shared earlier by non-administrators. Administrators can also review existing shared server entries for suspicious names or destinations, especially hosts controlled outside the organization.

CVE-2026-116248: pgAdmin 4: Non-administrators can share a server with every user

Event History

Frequently Asked Questions

Who can exploit this issue?

What must happen for credentials to be exposed?

Are default deployments affected?

What can be done before upgrading?

How can administrators identify possible prior abuse?

Company

Resources

Contact

Frequently Asked Questions

Who can exploit this issue?

What must happen for credentials to be exposed?

Are default deployments affected?

What can be done before upgrading?

How can administrators identify possible prior abuse?