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.
Advisories
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-4905-1 | postgresql-15 security update |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Fri, 13 Nov 2026 00:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-205 | |
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Fri, 13 Nov 2026 00:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Postgresql
Postgresql postgresql |
|
| Vendors & Products |
Postgresql
Postgresql postgresql |
Thu, 12 Nov 2026 14:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | PostgreSQL security_barrier analysis can expose hidden values through indirect expressions | |
| Weaknesses | CWE-862 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: PostgreSQL
Published:
Updated: 2026-11-12T14:15:15.661Z
Reserved: 2026-10-26T03:52:44.053Z
Link: CVE-2026-116327
No data.
Status : Awaiting Analysis
Published: 2026-11-12T15:17:41.197
Modified: 2026-11-12T19:02:35.830
Link: CVE-2026-116327
OpenCVE Enrichment
Updated: 2026-11-14T22:00:01Z
Debian DLA