Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-12050Published 2026-06-18

CVE-2026-12050 — pgadmin.org pgAdmin 4

mediumPublic exploit1 PoC repo

As of 2026-06-22, CVE-2026-12050 is a MEDIUM-severity vulnerability in pgadmin.org pgAdmin 4, CVSS v3.1 4.3, EPSS 0.4% (34.9th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-12050, 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.4%Higher than 34.9% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
1Campaigns referencing it
Priority
5.5/10Threadlinqs triage score
Published
Updated 2026-06-22
CVSS v3.1 4.3 (MEDIUM) · CVSS v4.0 5.3 · EPSS 0.4% (higher than 34.9% of all scored CVEs) · Priority 5.5/10 · Published 2026-06-18

Last updated:

What is CVE-2026-12050?

SQL injection in pgAdmin 4's named restore point endpoint (POST /browser/server/restore_point/{gid}/{sid}). The user-supplied 'value' field was interpolated directly into the SQL string with str.format() instead of being passed as a bound parameter, allowing an authenticated pgAdmin user with a connected PostgreSQL session to inject additional statements through that endpoint. The injected SQL executes under the database role the user is already authenticated as. The defect does not cross a privilege boundary -- the user already has direct SQL access to that role through the Query Tool -- so the attacker gains no capability beyond what their database role already grants them. The marginal impact accounts for the fact that the injection path is not the documented SQL-execution interface, so a deployment that gates the Query Tool at the application layer could see SQL executed through a path it did not anticipate. Fix passes the restore point name as a bound parameter and schema-qualifies the function call as pg_catalog.pg_create_restore_point so a non-default search_path on the connection cannot redirect the call to a shadow definition. A regression test asserts the value arrives as a bound parameter and not spliced into the SQL string. This issue affects pgAdmin 4: from 1.0 before 9.16.

The record classifies CVE-2026-12050 under weakness class CWE-89. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs low-privilege credentials, needs no user interaction. 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:L/UI:N/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:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
EPSS (FIRST)
0.4% probability of exploitation in the next 30 days, higher than 34.9% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
5.5/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-06-18

Is CVE-2026-12050 being exploited?

Weaponised exploit code for CVE-2026-12050 is publicly available. 1 public proof-of-concept repository is tracked for this identifier. It currently carries a trending score of 23 in the Threadlinqs vulnerability feed.

Affected products and versions

How to fix CVE-2026-12050

Patch reference: https://github.com/pgadmin-org/pgadmin4/commit/3379c39865d3ab6f52afce97361fb16bcdd77cd2. 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-12050

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

Sources

Enriched from CVE.org, FIRST EPSS, public proof-of-concept repositories.

Vendor advisory and patch

Issue tracking and product pages