CVEvulnerability

CVE-2026-7817

7.1 HIGH Published 2026-05-11 Modified 2026-10-26 Official page ↗
Status
Analyzed
Published
2026-05-11
Last modified
2026-10-26
Assigner
f86ef6dc-4d3a-42ad-8f28-e6d5547a5007
CVSS 4.0 (f86ef6dc-4d3a-42ad-8f28-e6d5547a5007)
7.1 HIGH — 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/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
CVSS 3.1 (f86ef6dc-4d3a-42ad-8f28-e6d5547a5007)
6.5 MEDIUM — CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Weaknesses
CWE-552

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 configurations

• pgadmin pgadmin 4 (>= 9.13 < 9.15)

Related

Weakness · CWE (1)

  • CWE-552 Files or Directories Accessible to External Parties weakness

References