Loading vulnerability…
CVE-2026-1707 is an authenticated command execution vulnerability in pgAdmin affecting version 9.11 during restore operations in server mode. The flaw occurs when pgAdmin processes restores from PLAIN-format dump files using a restriction mechanism intended to disable dangerous psql meta-commands. During an active restore, an attacker with access to the pgAdmin web interface can observe the operation, extract the transient \restrict key in real time, and race the restore workflow by overwriting the restore script with attacker-controlled content that invokes \unrestrict using the disclosed key. This bypass re-enables meta-commands within the restore context and leads to reliable command execution on the pgAdmin host.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A pgAdmin vulnerability in version 9.11 involving restore restriction bypass that could lead to command execution during restore operations.
A pgAdmin 4 server-mode restore restriction bypass via key disclosure that allowed attackers to re-enable metacommands and achieve command execution on the pgAdmin host.
A prior pgAdmin server mode vulnerability involving a restore restriction bypass via key disclosure, mentioned as historical context.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.