This vulnerability leads to potentially incorrect policies being applied in cases where role-specific policies are used and a given query is planned under one role and then executed under other roles, which could happen under security definer functions or when a common user and query is planned initially and then re-used across multiple SET ROLEs. Applying an incorrect policy may permit a user to complete otherwise-forbidden reads and modifications. This affects only databases that have used CREATE POLICY to define a row security policy.
Acknowledgments: Name: the PostgreSQL project Upstream: Ashutosh Bapat
External references: http://www.postgresql.org/about/news/1656/
Upstream commit: http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=db69e58a0642ef7fa46d62f6c4cf2460c3a1b41b
Only PostgreSQL 9.5 was affected, which is not yet part of any Red Hat product.