CVE-2026-12049 Details
Description
Open redirect in pgAdmin 4's multi-factor authentication flow. The MFA validate and register endpoints honoured the user-supplied 'next' query/form parameter without confirming the target pointed back inside pgAdmin, so an authenticated victim who clicked /mfa/validate?next=<external> -- a link typically delivered by phishing -- would be sent to an attacker-controlled host directly out of the trusted auth flow. The defect is a trusted-domain redirect, not a privilege bypass: the attacker gains no read/write access to pgAdmin or the victim's database, but the redirect launders the attacker's destination through pgAdmin's URL, which raises the success rate of credential-phishing follow-on against the victim. Fix introduces a same-origin _is_safe_redirect_url helper and gates every MFA redirect that consumes user-supplied 'next' values through it. The helper allows only relative paths and absolute URLs whose scheme is http(s) and whose host matches the current request host; it rejects external hosts in absolute and protocol-relative form, non-http schemes (javascript:, data:, mailto:), userinfo tricks (http://localhost@attacker/), and backslash variants that some browsers normalize to forward slashes. Unsafe targets fall back to the internal browser index. A dedicated regression test exercises each accept/reject category and the original reporter PoC. This issue affects pgAdmin 4: from 6.0 before 9.16.
A trusted-domain open redirect vulnerability has been identified in pgAdmin 4 versions 6.0 prior to 9.16, within the multi-factor authentication (MFA) process. The issue arises because the MFA validate and register endpoints accepted user-supplied 'next' parameters without verifying if the target URL was internal to pgAdmin. This flaw allowed an authenticated user to be redirected to an external, attacker-controlled site, bypassing the trusted authentication flow. While the vulnerability does not grant access to pgAdmin or the user's database, it facilitates credential phishing by laundering the attacker's URL through pgAdmin's trusted domain.
Users can update to pgAdmin 4 version 9.16 or later, where this vulnerability has been fixed. Instructions for updating can be found in the pgAdmin 4 release notes for version 9.16.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jun 22, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/pgadmin-org/pgadmin4/commit/fff6a481854b07822c2b54e8181e6a9076d204cd | PostgreSQL | Patch |
| https://github.com/pgadmin-org/pgadmin4/issues/10028 | PostgreSQL | Issue TrackingPatch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-601 | URL Redirection to Untrusted Site ('Open Redirect') | PostgreSQL |
Affected Products
| Product | Versions |
|---|---|
| pgadmin pgadmin 4 | >= 6.0, < 9.16 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 26, 2026 | CVE Translated | [email protected] |
| Jun 29, 2026 | Initial Analysis | [email protected] |
| Jun 22, 2026 | CVE Modified | CISA-ADP |
| Jun 19, 2026 | New CVE Received | PostgreSQL |