Loading vulnerability…
CVE-2026-14666 is an authorization flaw in PostgreSQL row-level security (RLS) plan caching. PostgreSQL incompletely tracks changes to role membership, role attributes, and database ownership when determining whether cached RLS policy information must be invalidated. Consequently, a reused query plan can continue to apply an RLS policy cached before a privilege or ownership change, rather than the policy that should apply after the change. The stale policy remains effective until another cache-invalidating event occurs or the affected session terminates. PostgreSQL versions before 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
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.
23 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A PostgreSQL vulnerability referenced by the plugin; no technical vulnerability details are provided.
A PostgreSQL row-security caching flaw that fails to account for role modifications.
A PostgreSQL row-security caching flaw that disregards role modifications.
A PostgreSQL row-security caching flaw that fails to account for role modifications.
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.