Skip to main content
Mallory
MediumVulnerability

CVE-2026-116311: PostgreSQL DROP OWNED Row-Level Security Bypass

Published Nov 12, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days10 mentions · peak 4 in a dayToday
CVSS5.4Medium · v3.1
EPSS0.23%14th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-116311CWE-862 · Missing Authorization

A missing authorization check in PostgreSQL DROP OWNED allows an unprivileged database role to remove itself from restrictive row-level security policies on tables it does not own. Subsequent queries can then read or modify rows that those policies were intended to deny. Affected releases are PostgreSQL 18 before 18.7, 17 before 17.12, 16 before 16.16, 15 before 15.20, and 14 before 14.25.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An authenticated database user can bypass restrictive row-level security controls, compromising the confidentiality and integrity of protected rows. The bypass affects subsequent queries after DROP OWNED and does not require ownership of the affected tables. This vulnerability has a CVSS v3.1 base score of 5.4.

Remediation

Patch, then assume compromise.

Upgrade to PostgreSQL 18.7, 17.12, 16.16, 15.20, or 14.25, or a later fixed release in the corresponding branch. For Debian 12 PostgreSQL 15 packages, upgrade to version 15.20-0+deb12u1 or later. PostgreSQL 14.25 is the final release of that branch; migrate PostgreSQL 14 deployments to a supported major version for continued security maintenance.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-116311 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-116311 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-116311?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-116311.
Is there a patch for CVE-2026-116311?
Upgrade to PostgreSQL 18.7, 17.12, 16.16, 15.20, or 14.25, or a later fixed release in the corresponding branch. For Debian 12 PostgreSQL 15 packages, upgrade to version 15.20-0+deb12u1 or later.
How severe is CVE-2026-116311?
CVE-2026-116311 has a CVSS v3.1 score of 5.4 (Medium) and an EPSS score of 0.23% (14th percentile) as of Nov 17, 2026.
Activity feed

Recent activity

10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+2 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.