pgAdmin 4: SQL injection in named restore point endpoint
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-12050
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 2 Nov 2026, 20:14 UTC · Revision 1
Source evidence
pgAdmin 4: SQL injection in named restore point endpoint
core-osv · Original sourcePublished 18 Jun 2026, 23:37 UTC
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.
osv:CVE-2026-12050
Complete source record
{
"id": "73aa8749ab2d8f7fa9d3116896d4f48a918804cb136159e0bdf240107b562460",
"url": "https://osv.dev/vulnerability/CVE-2026-12050",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "pgAdmin 4: SQL injection in named restore point endpoint",
"summary": "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.",
"evidence": "osv:CVE-2026-12050",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2026-12050",
"aliases": [
"CVE-2026-12050"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "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"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/pgadmin-org/pgadmin4",
"type": "GIT",
"events": [
{
"introduced": "30397476da45e419a409710e7447bf0f10fcbcd9"
},
{
"fixed": "888a053231923e6704b56165cf248db056252144"
},
{
"fixed": "3379c39865d3ab6f52afce97361fb16bcdd77cd2"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:pgadmin:pgadmin_4:*:*:*:*:*:postgresql:*:*",
"range": [
{
"introduced": "1.0"
},
{
"fixed": "9.16"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "3379c39865d3ab6f52afce97361fb16bcdd77cd2"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"versions": [
"REL-9_15",
"REL-9_14",
"REL-9_13",
"REL-9_12",
"REL-9_11",
"REL-9_10",
"REL-9_9",
"REL-9_8",
"REL-9_7",
"REL-9_6",
"REL-9_5",
"REL-9_4",
"REL-9_3",
"REL-9_2",
"REL-9_1",
"REL-9_0",
"REL-8_14",
"REL-8_13",
"REL-8_12",
"REL-8_11",
"REL-8_10",
"REL-8_9",
"REL-8_8",
"REL-8_7",
"REL-8_6",
"REL-8_5",
"REL-8_4",
"REL-8_3",
"REL-8_2",
"REL-8_1",
"REL-8_0",
"REL-7_8",
"REL-7_7",
"REL-7_6",
"REL-7_5",
"REL-7_4",
"REL-7_3",
"REL-7_2",
"REL-7_1",
"REL-7_0",
"REL-6_21",
"REL-6_20",
"REL-6_19",
"REL-6_18",
"REL-6_17",
"REL-6_16",
"REL-6_15",
"REL-6_14",
"REL-6_13",
"REL-6_12",
"REL-6_11",
"REL-6_10",
"REL-6_9",
"REL-6_8",
"REL-6_7",
"REL-6_6",
"REL-6_5",
"REL-6_4",
"REL-6_3",
"REL-6_2",
"REL-6_1",
"REL-6_0",
"REL-5_7",
"REL-5_6",
"REL-5_5",
"REL-5_4",
"REL-5_3",
"REL-5_2",
"REL-5_1",
"REL-5_0",
"REL-4_30",
"REL-4_29",
"REL-4_28",
"REL-4_27",
"REL-4_26",
"REL-4_25",
"REL-4_24",
"REL-4_23",
"REL-4_22",
"REL-4_21",
"REL-4_20",
"REL-4_19",
"REL-4_18",
"REL-4_17",
"REL-4_16",
"REL-4_15",
"REL-4_14",
"REL-4_13",
"REL-4_12",
"REL-4_11",
"REL-4_10",
"REL-4_9",
"REL-4_8",
"REL-4_7",
"REL-4_6",
"REL-4_5",
"REL-4_4",
"REL-4_3",
"REL-4_2",
"REL-4_1",
"REL-4_0",
"REL-3_6",
"REL-3_5",
"REL-3_4",
"REL-3_3",
"REL-3_2",
"REL-3_1",
"REL-3_0",
"REL-2_1",
"REL-2_0",
"REL-2_0-RC2",
"REL-2_0-RC1",
"REL-1_6",
"REL-1_5",
"REL-1_4",
"REL-1_3",
"REL-1_2",
"REL-1_1",
"REL-1_0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-12050.json"
}
}
],
"modified": "2026-10-28T02:30:23.173595756Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/12xxx/CVE-2026-12050.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-12050",
"https://github.com/pgadmin-org/pgadmin4/issues/10026",
"https://github.com/pgadmin-org/pgadmin4/commit/3379c39865d3ab6f52afce97361fb16bcdd77cd2",
"https://github.com/pgadmin-org/pgadmin4"
],
"provider_metadata": {
"cwe_ids": [
"CWE-89"
],
"cna_assigner": "PostgreSQL",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/12xxx/CVE-2026-12050.json"
}
},
"related_cves": [
{
"value": "CVE-2026-12050",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 489725,
"published_at": "2026-06-18T23:37:19.384+00:00"
}