CVE-2026-116327 · Runtime
NO FIX YET · SEE WHAT TO DO
A database user with query access can apply a leaky function to a CASE test value or internal parameter and infer column values hidden by a security_barrier view. The attacker gets read access to protected data they should not see, one inferred value at a time.
first public Nov 12, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Only servers running PostgreSQL versions before 18.7, 17.12, 16.16, 15.20 or 14.25 are affected, and only where users with query access rely on security_barrier views to hide columns. Databases without security_barrier views or without untrusted database users can deprioritize this.
Not affected if managed-hosting, no-security-barrier-views, trusted-users-only
Who cares database, postgresql, self-hosted
SELECT version(); in psql and compare against the fixed versions below.security_barrier (\d+ viewname shows the option) that hide sensitive columns from other roles.18.7, 17.12, 16.16, 15.20, 14.25 (affected: versions before these)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.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.