Quick answers
- Is CVE-2026-12050 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-12050 being exploited in the wild.
- How severe is CVE-2026-12050?
- Medium severity, with a CVSS score of 4.3, published 19 June 2026.
- Which products and versions are affected?
- pgadmin.org pgAdmin 4 1.0 to 9.15.
- Is there a fix for CVE-2026-12050?
- A patch was published on 2026-06-19: Fix released in version 9.16 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-12050 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-12050?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A SQL injection vulnerability exists in pgAdmin 4's 'named restore point' endpoint (POST /browser/server/restore_point/{gid}/{sid}). The root cause is the use of Python's str.format() to interpolate the user-supplied 'value' field directly into a SQL string instead of using bound parameters. An authenticated attacker with an active database session can inject additional SQL statements that execute with the privileges of their current database role. While this does not typically cross a privilege boundary (as users often have direct SQL access via the Query Tool), it allows for the bypass of application-layer controls that might restrict the standard Query Tool. The vulnerability is fixed in version 9.16 by implementing parameterized queries and schema-qualifying the function call.
Affected products
- pgadmin.org pgAdmin 4 1.0 to 9.15
Timeline
- 2026-06-08: disclosed: Issue opened on GitHub
- 2026-06-18: advisory: NVD publication date
- 2026-06-19: patched: Fix released in version 9.16