Is CVE-2026-7817 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-7817 being exploited in the wild.

How severe is CVE-2026-7817?

Medium severity, with a CVSS score of 6.5, published 11 May 2026.

Which products and versions are affected?

PostgreSQL pgAdmin 4 >= 9.13, < 9.15; pgadmin4 (PyPI) < 9.15, ECOSYSTEM:introduced=0,fixed=9.15.

Is there a fix for CVE-2026-7817?

Yes. pgadmin4 (PyPI): upgrade to 9.15 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-7817 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-7817?

Check whether you run PostgreSQL pgAdmin 4 or pgadmin4 (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-7817: PostgreSQL pgAdmin 4 LFI and SSRF in LLM API endpoints

Q: Is there a fix for CVE-2026-7817?

Yes. pgadmin4 (PyPI): upgrade to 9.15 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-7817 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-7817?

Check whether you run PostgreSQL pgAdmin 4 or pgadmin4 (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-7817 · Severity: medium · CVSS 6.5 · Published 2026-05-11

pgAdmin 4 is a popular management tool for PostgreSQL databases. A security flaw in its Large Language Model (LLM) integration allows authenticated users to read sensitive files from the server's filesystem or force the server to make unauthorized requests to internal network services. This could lead to the exposure of configuration secrets, system credentials, or access to private cloud metadata services.

Technologies: PostgreSQL pgAdmin 4, pgadmin4 (PyPI). Vendors: PostgreSQL, PyPI.

Quick answers

Is CVE-2026-7817 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-7817 being exploited in the wild.
How severe is CVE-2026-7817?: Medium severity, with a CVSS score of 6.5, published 11 May 2026.
Which products and versions are affected?: PostgreSQL pgAdmin 4 >= 9.13, < 9.15; pgadmin4 (PyPI) < 9.15, ECOSYSTEM:introduced=0,fixed=9.15.
Is there a fix for CVE-2026-7817?: Yes. pgadmin4 (PyPI): upgrade to 9.15 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-7817 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-7817?: Check whether you run PostgreSQL pgAdmin 4 or pgadmin4 (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

pgadmin4 (PyPI): upgrade to 9.15 or later
```
pip install "pgadmin4>=9.15"
```

Technical details

The vulnerability exists in the LLM provider client configuration where 'api_key_file' and 'api_url' parameters are processed without adequate validation. An authenticated attacker can exploit the LFI by setting 'api_key_file' to an arbitrary path, allowing them to read any file accessible by the pgAdmin process. Additionally, the SSRF vulnerability allows attackers to manipulate 'api_url' to probe internal network targets or access cloud metadata services (e.g., 169.254.169.254) via the chat and model-list endpoints. The fix implemented in version 9.15 restricts file access to specific user directories, enforces a 1024-byte read limit, and introduces an allow-list for API URLs.

Affected products

PostgreSQL pgAdmin 4 >= 9.13, < 9.15

Identifiers

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

Timeline

2026-05-01: disclosed: Issue reported on GitHub
2026-05-11: advisory: CVE published and NVD entry created
2026-05-11: patched: Fixed in version 9.15

References

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

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.