CVE-2026-7817: pgAdmin 4: Local file inclusion and server-side request forgery in LLM API configuration endpoints

Published May 11, 2026
·
Updated

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 pointing apikeyfile 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 apiurl, exploiting the chat path and model-list endpoints.

Fix restricts apikeyfile 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 apiurl against a configurable allow-list (config.ALLOWEDLLMAPIURLS) at every entry point.

This issue affects pgAdmin 4: before 9.15.

Affected Software

2 affected components
pgAdmin pgAdmin 4<9.15
pgAdmin Pgadmin 4 Postgresql>=9.13<9.15

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pgAdmin 4 to a version that resolves this vulnerability.

    Fixed in 9.15
  2. Configuration

    Validate api_key_file to allow only paths in the user's private storage (server mode) or home directory (desktop mode). Enforce that the API key matches a printable-ASCII shape and cap reads to 1024 bytes.

    pgAdmin 4 LLM API configuration endpoints api_key_file = restricted to user's private storage (server mode) or home directory (desktop mode) + printable-ASCII key shape + 1024-byte read cap
  3. Configuration

    Validate api_url against the configurable allow-list config.ALLOWED_LLM_API_URLS at every entry point (including chat path and model-list endpoints) to prevent SSRF to internal targets (e.g., 169.254.169.254).

    pgAdmin 4 LLM API configuration endpoints api_url = gated by config.ALLOWED_LLM_API_URLS allow-list at every entry point

Event History

May 11, 2026
CVE Published
via MITRE·02:35 PM
Data Sourced
via MITRE·02:35 PM
DescriptionSeverity
Data Sourced
via NVD·04:17 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-7817?

The severity of CVE-2026-7817 is rated high with a score of 7.1.

2

What vulnerabilities are associated with CVE-2026-7817?

CVE-2026-7817 involves local file inclusion (LFI) and server-side request forgery (SSRF) vulnerabilities.

3

How do I fix CVE-2026-7817?

A patch is available to remediate the vulnerabilities in CVE-2026-7817.

4

What can an attacker do with CVE-2026-7817?

An authenticated attacker could read arbitrary server-side files due to the vulnerabilities in CVE-2026-7817.

5

Which software is affected by CVE-2026-7817?

The affected software for CVE-2026-7817 is pgAdmin 4.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203