CVE-2026-116327

PostgreSQL security_barrier analysis can expose hidden values through indirect expressions

  • Medium 4.3

Description

Exposure of sensitive information in PostgreSQL security_barrier processing allows a database user to infer values hidden by a security_barrier view, via applying a leaky function to a CASE test value or internal parameter that indirectly represents a protected column. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.

Key facts

Published
12 Nov 2026
Last changed
12 Nov 2026
Assigned by
PostgreSQL
EPSS
0.224% likely to be exploited in the next 30 days, higher than 13.124% of CVEs (scores for 15 Nov 2026)

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 4.3CVSS 3.1, Mediumfrom the CNA (PostgreSQL)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
n/aPostgreSQL
  • Default status: unaffected
  • 18 up to but excluding 18.7 (affected)
  • 17 up to but excluding 17.12 (affected)
  • 16 up to but excluding 16.16 (affected)
  • 15 up to but excluding 15.20 (affected)
  • 0 up to but excluding 14.25 (affected)

Timeline

  1. 12 Nov 2026 Published

Weakness

References