Skip to content

GHSA-p58c-q354-6c4f CVE-2026-7817 PYSEC-2026-2871

pgAdmin 4 contains local file inclusion (LFI) and server-side request forgery (SSRF) vulnerabilities

Medium PyPI
Severity
0.0 / 10
Medium · CVSS 4.0
Exploit chance (EPSS)
0.22%
Chance of exploitation in the next 30 days. Higher than 12.19% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-552 Files or Directories Accessible to External Parties
Fix
9.15
Upgrade pgadmin4 to this version or later

Description

Local file inclusion (LFI) and server-side request forgery (SSRF) vulnerabilities in pgAdmin 4 LLM API configuration endpoints.

User-supplied api_key_file and api_url preferences were passed to the LLM provider clients without validation. An authenticated user could read arbitrary server-side files by pointing api_key_file at any path readable by the pgAdmin process, or coerce pgAdmin into making requests to internal targets (e.g. cloud metadata services such as 169.254.169.254) by setting api_url, exploiting the chat path and model-list endpoints.

Fix restricts api_key_file to the user's private storage (server mode) or home directory (desktop mode), enforces a printable-ASCII key shape and a 1024-byte read cap, and gates api_url against a configurable allow-list (config.ALLOWED_LLM_API_URLS) at every entry point.

This issue affects pgAdmin 4: before 9.15.

Affected versions

PyPI

PackageVulnerableFixed in
pgadmin4
< 9.15
9.15

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

pgadmin4 PyPI → 9.15

pip
pip install --upgrade "pgadmin4>=9.15"
poetry
poetry add "pgadmin4>=9.15"
uv
uv add "pgadmin4>=9.15"

Severity breakdown

CVSS 4.0 0.0

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Attack vector
Network
Attack complexity
Low
Attack requirements
None
Privileges required
Low
User interaction
None
Confidentiality (vulnerable system)
High
Integrity (vulnerable system)
None
Availability (vulnerable system)
None
Confidentiality (subsequent systems)
None
Integrity (subsequent systems)
None
Availability (subsequent systems)
None

CVSS 3.1 6.5

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Weakness

CWE-552: Files or Directories Accessible to External Parties

The product makes files or directories accessible to unauthorized actors, even though they should not be.

How to prevent it
  • Implementation, System Configuration, Operation: When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to disable public access.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-hv9p-2pqf-r5w3
pgAdmin 4: Improper restriction of excessive authentication attempts
Medium Also affects pgadmin4
GHSA-hr4r-fwpv-c95j
pgAdmin 4 File Manager has symbolic-link path traversal
High Also affects pgadmin4
GHSA-4rhg-h8f2-v4jm
pgAdmin 4 has deserialization of untrusted data in its FileBackedSessionManager
High Also affects pgadmin4
GHSA-j74f-g7vx-fh4x
pgAdmin 4: OS command injection vulnerability in Import/Export query export
High Also affects pgadmin4
GHSA-hp84-p2gq-6fvr
SQL injection vulnerability in pgAdmin 4 Maintenance Tool
High Also affects pgadmin4
GHSA-6p2c-69cv-3fxq
pgAdmin 4: Stored cross-site scripting (XSS) vulnerability in Browser Tree and Explain Visualizer modules
Medium Also affects pgadmin4
GHSA-h2x2-q2mc-24gw
pgAdmin 4 server mode has an authorization vulnerability affecting Server Groups, Servers, Shared Servers, Background Processes, and Debugger modules
Critical Also affects pgadmin4
GHSA-3p7x-94q9-jq9x
pgadmin4 affected by a Restore restriction bypass via key disclosure vulnerability
Medium Also affects pgadmin4
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor