A missing authorization check in PostgreSQL CREATE TYPE allows creation of a multirange type in a schema without properly enforcing the required CREATE privilege on that schema. This privilege-check omission enables an attacker who can create database objects to place a user-defined type where PostgreSQL type resolution via search_path can later select it, including in cases involving extension-defined types. As a result, subsequent queries executed by another user can be hijacked so that the victim executes arbitrary SQL functions chosen by the attacker. Affected versions are PostgreSQL releases before 18.4, 17.10, 16.14, 15.18, and 14.23.
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.
15 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability in PostgreSQL addressed indirectly through upgraded third-party components in Tenable Security Center.
A PostgreSQL vulnerability described as enabling privilege bypass and arbitrary SQL execution.
A PostgreSQL privilege-check bypass vulnerability allowing multirange types to be created in a schema without properly enforcing CREATE privilege checks.
A PostgreSQL privilege-check bypass vulnerability where creating a multirange type in a different schema failed to enforce the required CREATE privilege on that schema.
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.