Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-7817: Local file inclusion (LFI) and server-side request forgery (SSRF) vulnerabilities in pgAdmin 4 LLM API configu

26
Routine
MEDIUM 6.5UPGRADE

CVE-2026-7817 is a medium-severity flaw (CVSS 6.5) affecting pgadmin 4. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

  • No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score6.5 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance0.2% (top 88%)
CISA exploited listNo
WeaknessCWE-552
Published2026-05-11
Last modified2026-10-26
Publisher (CNA): PostgreSQL · Vendor: pgadmin

Share: LinkedIn · X · Reddit

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

pgadmin pgadmin 4 UPGRADE
Affected: >= 9.13 and < 9.15
Fixed in: 9.15
Safe to downgrade to: a release before 9.13
1. Check installed version
apt-cache policy pgadmin-4 || rpm -q pgadmin-4 || pgadmin-4 --version
2. UPGRADE to 9.15 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade pgadmin-4
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade pgadmin-4
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 9.13 (Debian / Ubuntu)
apt-cache madison pgadmin-4 sudo apt install pgadmin-4=<VERSION_BEFORE_9.13> sudo apt-mark hold pgadmin-4
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list pgadmin-4 sudo dnf downgrade pgadmin-4-<VERSION_BEFORE_9.13> sudo dnf versionlock add pgadmin-4
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-7817?

pgadmin 4: upgrade to 9.15. Exact commands for each OS are on this page.

Is CVE-2026-7817 being exploited?

CVE-2026-7817 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-7817 affect?

CVE-2026-7817 affects pgadmin 4. Severity is medium (CVSS 6.5). 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.

How urgent is CVE-2026-7817?

Priority 26/100. No elevated risk signals yet.

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.