CVE-2026-116311: PostgreSQL DROP OWNED can remove restrictive row security policies from non-owned tables

Is it exploited?

Not on CISA's list. CISA has not added it to the Known Exploited Vulnerabilities catalog as of 10 Nov 2026. If CISA adds it, this page shows it as known exploited.

How likely is exploitation in the next 30 days?

Not yet scored. FIRST's EPSS model has no score for this record as of 12 Nov 2026.

How severe?

5.4 Medium

CVSS v3.1 base score, given by the CNA

What should I do?

CISA has set no required action, because the vulnerability is not in KEV.

No patch or vendor advisory is listed in the CVE record. Check PostgreSQL's advisories.

Which versions are affected?

Affected

• from 18 to before 18.7
• from 17 to before 17.12
• from 16 to before 16.16
• from 15 to before 15.20
• before 14.25

Versions by product

Source: CISA KEV 2026.11.10, as of 10 Nov 2026; FIRST EPSS, as of 12 Nov 2026; CVE List, as of 13 Nov 2026. About the data.

Description

PostgreSQL DROP OWNED can remove restrictive row security policies from non-owned tables

Missing authorization in PostgreSQL DROP OWNED allows a role to remove itself from restrictive row level security policies, thereby reading or modifying rows that the policy was intended to deny, via queries after the DROP OWNED. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.

Source: CVE List, as of 13 Nov 2026. About the data.

What to do

Advisories and patches

No patch, vendor advisory or mitigation is listed in the CVE record. Check PostgreSQL's own security advisories for a fix, and compare your version with the affected versions below.

This summary is based on the CVE record as of 13 Nov 2026. Check the vendor's advisory before you act: affected versions and fixes can change.

Affected products and versions

Source: CVE List, as of 13 Nov 2026. About the data.

Timeline