Row security policies disregard user ID changes after inlining; PostgreSQL could permit incorrect policies to be applied in certain cases where role-specific policies are used and a given query is planned under one role and then executed under other roles. This scenario can 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.
{
"license": "CC-BY-4.0",
"sources": [
{
"published": "2023-06-09T19:15:09.313Z",
"url": "https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2023-2455",
"modified": "2025-01-06T18:15:13.913Z",
"html_url": "https://nvd.nist.gov/vuln/detail/CVE-2023-2455",
"id": "CVE-2023-2455",
"imported": "2026-04-03T13:13:10.297Z"
}
]
}