CVE-2026-7817

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 88% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.5
EG Score
6.5(medium)
EPSS
12.1%
KEV
Not listed

Published

May 11, 2026

Last Modified

May 26, 2026

Advisory Details (1)

Auto-updated May 11, 2026
No patch confirmed yet.
generic

Local file inclusion and SSRF in LLM API configuration endpoints (CVE-2026-7817) · Issue #9900 · pgadmin-org/pgadmin4 · GitHub

https://github.com/pgadmin-org/pgadmin4/issues/9900

Vendor Advisories for CVE-2026-7817(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
pgadmin44.20 ... 9.9 (77 versions)9.15—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 45× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-09 19:10 UTCEPSS rescore
  3. 2026-07-09 19:10 UTCEPSS rescore
  4. 2026-07-08 15:16 UTCEPSS rescore
  5. 2026-07-08 15:16 UTCEPSS rescore
  6. 2026-07-07 13:46 UTCEPSS rescore
  7. 2026-07-07 13:46 UTCEPSS rescore
  8. 2026-07-06 16:27 UTCEPSS rescore
  9. 2026-07-06 16:27 UTCEPSS rescore
  10. 2026-07-06 02:23 UTCEPSS rescore
  11. 2026-07-06 02:23 UTCEPSS rescore
  12. 2026-07-05 02:31 UTCEPSS rescore
  13. 2026-07-05 02:30 UTCEPSS rescore
  14. 2026-07-04 06:31 UTCEPSS rescore
  15. 2026-07-04 06:31 UTCEPSS rescore
  16. 2026-07-01 15:07 UTCEPSS rescore
  17. 2026-06-30 23:22 UTCEPSS rescore
  18. 2026-06-29 14:06 UTCEPSS rescore
  19. 2026-06-28 14:07 UTCEPSS rescore
  20. 2026-06-28 08:46 UTCEG score recompute
  21. 2026-06-28 04:56 UTCEPSS rescore
  22. 2026-06-27 09:54 UTCEG score recompute
  23. 2026-06-27 03:08 UTCEPSS rescore
  24. 2026-06-26 05:09 UTCEG score recompute
  25. 2026-06-25 13:50 UTCEPSS rescore
Show 56 more
  1. 2026-06-24 14:05 UTCEPSS rescore
  2. 2026-06-23 21:33 UTCEPSS rescore
  3. 2026-06-22 14:25 UTCEPSS rescore
  4. 2026-06-21 14:56 UTCEPSS rescore
  5. 2026-06-21 01:59 UTCEPSS rescore
  6. 2026-06-19 19:26 UTCEPSS rescore
  7. 2026-06-18 17:52 UTCEPSS rescore
  8. 2026-06-17 17:53 UTCEPSS rescore
  9. 2026-06-17 05:35 UTCEG score recompute
  10. 2026-06-16 17:53 UTCEPSS rescore
  11. 2026-06-16 07:28 UTCEG score recompute
  12. 2026-06-15 17:49 UTCEPSS rescore
  13. 2026-06-15 17:49 UTCEPSS rescore
  14. 2026-06-15 00:12 UTCEG score recompute
  15. 2026-06-14 23:18 UTCEPSS rescore
  16. 2026-06-14 01:57 UTCEG score recompute
  17. 2026-06-13 23:00 UTCEPSS rescore
  18. 2026-06-12 23:12 UTCEPSS rescore
  19. 2026-06-12 23:12 UTCEPSS rescore
  20. 2026-06-12 12:44 UTCEG score recompute
  21. 2026-06-11 14:40 UTCEG score recompute
  22. 2026-06-11 14:00 UTCEPSS rescore
  23. 2026-06-10 22:19 UTCEPSS rescore
  24. 2026-06-10 16:36 UTCEG score recompute
  25. 2026-06-10 13:22 UTCEPSS rescore
  26. 2026-06-09 18:31 UTCEG score recompute
  27. 2026-06-08 20:27 UTCEG score recompute
  28. 2026-06-08 14:17 UTCEPSS rescore
  29. 2026-06-07 18:41 UTCEG score recompute
  30. 2026-06-07 15:25 UTCEPSS rescore
  31. 2026-06-06 20:37 UTCEG score recompute
  32. 2026-06-06 13:47 UTCEPSS rescore
  33. 2026-06-05 22:47 UTCEPSS rescore
  34. 2026-06-05 22:33 UTCEG score recompute
  35. 2026-06-05 06:10 UTCEPSS rescore
  36. 2026-06-05 00:29 UTCEG score recompute
  37. 2026-06-04 13:12 UTCEPSS rescore
  38. 2026-06-04 01:17 UTCEG score recompute
  39. 2026-06-03 03:13 UTCEG score recompute
  40. 2026-06-02 20:13 UTCEPSS rescore
  41. 2026-06-02 05:09 UTCEG score recompute
  42. 2026-06-01 13:52 UTCEPSS rescore
  43. 2026-06-01 07:05 UTCEG score recompute
  44. 2026-05-31 22:30 UTCEPSS rescore
  45. 2026-05-31 00:16 UTCEPSS rescore
  46. 2026-05-29 13:44 UTCEPSS rescore
  47. 2026-05-28 13:44 UTCEPSS rescore
  48. 2026-05-27 13:40 UTCEPSS rescore
  49. 2026-05-27 13:40 UTCEPSS rescore
  50. 2026-05-26 13:44 UTCEPSS rescore
  51. 2026-05-26 07:18 UTCEPSS rescore
  52. 2026-05-23 00:07 UTCEG score recompute
  53. 2026-05-21 22:43 UTCEPSS rescore
  54. 2026-05-20 22:38 UTCEPSS rescore
  55. 2026-05-20 13:17 UTCEG score recompute
  56. 2026-05-20 11:22 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-7817?
CVE-2026-7817 is a medium vulnerability published on May 11, 2026. Local file inclusion (LFI) and server-side request forgery (SSRF) vulnerabilities in pgAdmin 4 LLM API configuration endpoints. User-supplied apikeyfile and apiurl preferences were passed to the LLM provider clients without validation. An authenticated user could read arbitrary server-side files by…
When was CVE-2026-7817 disclosed?
CVE-2026-7817 was first published in the National Vulnerability Database on May 11, 2026, with the most recent update on May 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-7817 actively exploited?
CVE-2026-7817 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 12.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-7817?
CVE-2026-7817 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-7817?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-7817, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-7817

Explore →

Is Your Infrastructure Affected by CVE-2026-7817?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs