# CVE-2024-10976

## Summary

- **CVE ID:** CVE-2024-10976
- **Severity:** MEDIUM
- **CVSS Score:** 4.2 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N)
- **CWE:** CWE-1250
- **Published:** Nov 14, 2024
- **Last Modified:** Mar 13, 2026

## Description

Incomplete tracking in PostgreSQL of tables with row security allows a reused query to view or change different rows from those intended.  CVE-2023-2455 and CVE-2016-2193 fixed most interaction between row security and user ID changes.  They missed cases where a subquery, WITH query, security invoker view, or SQL-language function references a table with a row-level security policy.  This has the same consequences as the two earlier CVEs.  That is to say, it 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.  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.  An attacker must tailor an attack to a particular application's pattern of query plan reuse, user ID changes, and role-specific row security policies.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.

## Affected Products

- n/a — PostgreSQL (17)
- n/a — PostgreSQL (16)
- n/a — PostgreSQL (15)
- n/a — PostgreSQL (14)
- n/a — PostgreSQL (13)
- n/a — PostgreSQL (0)

## References

- [CNA](https://www.postgresql.org/support/security/CVE-2024-10976/)
- [CVE](https://security.netapp.com/advisory/ntap-20250509-0010/)
- [CVE](https://lists.debian.org/debian-lts-announce/2024/11/msg00011.html)

## Exploitation Prediction (EPSS)

- **EPSS Score:** 0.77%
- **EPSS Percentile:** 53.4

---
_Exported from OnDuty AI Vulnerability Intelligence on 2026-09-11._