CVE-2026-7817
MEDIUMDescription
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.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 12% of all known CVEs.
References
Related Vulnerabilities
Other CWE-552 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2020-17519 | High | 7.5 | 98% | KEV | Fix |
| CVE-2025-11371 | High | 7.5 | 92% | KEV | Fix |
| CVE-2023-50164 | Critical | 9.8 | 81% | - | Fix |
| CVE-2016-3715 | Medium | 5.5 | 75% | KEV | Fix |
| CVE-2020-15175 | High | 7.4 | 72% | - | Fix |
| CVE-2021-39316 | High | 7.5 | 66% | - | - |
Common questions
How do I fix CVE-2026-7817?
Upgrade pgadmin 4 to 9.15 or later.
Is CVE-2026-7817 being actively exploited?
Not that we know of. CVE-2026-7817 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.22% is the estimated probability that it will be exploited in the next 30 days. That is higher than 12% of all scored CVEs.
How severe is CVE-2026-7817?
CVE-2026-7817 has a CVSS v3 base score of 6.5, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-7817 affect?
Published advisories record a fix for pgadmin 4 (NVD). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-7817
Markdown
[](https://tridentstack.com/cve/CVE-2026-7817)HTML
<a href="https://tridentstack.com/cve/CVE-2026-7817"><img src="https://tridentstack.com/cve/badge/CVE-2026-7817.svg" alt="CVE-2026-7817"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-05-26.