Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-12049Published 2026-06-18

CVE-2026-12049 — pgadmin.org pgAdmin 4

medium

As of 2026-06-22, CVE-2026-12049 is a MEDIUM-severity vulnerability in pgadmin.org pgAdmin 4, CVSS v3.1 4.3, EPSS 0.3% (30.1th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-12049, most recently “pgAdmin 4 v9.16 Patches 7 Vulnerabilities (CVE-2026-12044 to CVE-2026-12050): SQLi, AI-Assistant Read-Only Bypass to RCE, Auth Bypass with Pickle Deserialization, Stored XSS”.

CVSS v3.1
4.3/10Medium
EPSS
0.3%Higher than 30.1% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
1Campaigns referencing it
Priority
3.4/10Threadlinqs triage score
Published
Updated 2026-06-22
CVSS v3.1 4.3 (MEDIUM) · CVSS v4.0 5.3 · EPSS 0.3% (higher than 30.1% of all scored CVEs) · Priority 3.4/10 · Published 2026-06-18

Last updated:

What is CVE-2026-12049?

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= -- 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.

The record classifies CVE-2026-12049 under weakness class CWE-601. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs a user to take an action first. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 154 days ago.

Severity and exploitation probability

CVSS v3.1 base score
4.3 — MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
CVSS v4.0 base score
5.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
EPSS (FIRST)
0.3% probability of exploitation in the next 30 days, higher than 30.1% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
3.4/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-06-18

Is CVE-2026-12049 being exploited?

It currently carries a trending score of 14 in the Threadlinqs vulnerability feed.

Affected products and versions

How to fix CVE-2026-12049

Patch reference: https://github.com/pgadmin-org/pgadmin4/commit/fff6a481854b07822c2b54e8181e6a9076d204cd. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

Threat activity tracking CVE-2026-12049

1 tracked threat in the Threadlinqs corpus references CVE-2026-12049, either in the campaign’s CVE list or as an indicator on the campaign record.

Sources

Enriched from CVE.org, FIRST EPSS.

Vendor advisory and patch

Issue tracking and product pages