Skip to main content
Mallory
MediumVulnerability

CVE-2026-120154: PostgreSQL INSERT ON CONFLICT Row-Level Security Bypass

Published Nov 12, 2026 · Updated 2 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days11 mentions · peak 5 in a dayToday
CVSS4.3Medium · v3.1
EPSS0.29%22nd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-120154CWE-863

CVE-2026-120154 is a row-level security bypass in PostgreSQL INSERT ... ON CONFLICT DO UPDATE processing. Conflicting rows can be exposed to potentially information-leaking user qualification expressions before row-level security policies are checked. An attacker with INSERT, UPDATE, and applicable SELECT privileges on a table can repeatedly execute crafted statements to read every row, including rows hidden by those policies. Unlike CVE-2026-16237, this vulnerability does not enable unauthorized writes. Affected releases precede PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 in their respective branches.

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 authorized database user can bypass row-level security restrictions to disclose all rows in an affected table, compromising data isolation enforced through those policies. The vulnerability does not facilitate improper writes. Its CVSS v3.1 base score is 4.3.

Mitigation

If you can’t patch tonight, do this now.

Until an upgrade is possible, restrict untrusted roles' access to affected tables by removing at least one of the required INSERT, UPDATE, or applicable SELECT privileges where operationally feasible. Do not rely solely on row-security policies to protect those tables from roles retaining all required privileges.

Remediation

Patch, then assume compromise.

Upgrade to PostgreSQL 18.7, 17.12, 16.16, 15.20, or 14.25, as appropriate for the installed major version, or a later fixed release. The fix checks conflicting rows against row-level security policies before evaluating potentially information-leaking user qualifications. 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; plan migration to a supported major version.

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-120154 exploited in the wild?
As of Nov 16, 2026, Mallory has no reports of CVE-2026-120154 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-120154?
As of Nov 16, 2026, Mallory has found no public exploit for CVE-2026-120154.
Is there a patch for CVE-2026-120154?
Upgrade to PostgreSQL 18.7, 17.12, 16.16, 15.20, or 14.25, as appropriate for the installed major version, or a later fixed release. The fix checks conflicting rows against row-level security policies before evaluating potentially information-leaking user qualifications.
How severe is CVE-2026-120154?
CVE-2026-120154 has a CVSS v3.1 score of 4.3 (Medium) and an EPSS score of 0.29% (22nd percentile) as of Nov 16, 2026.
Activity feed

Recent activity

11 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 activity3Community discussion across Reddit, Mastodon, and other social sources.