Information Exposure Through Caching Affecting postgresql-upgrade package, versions *


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.18% (8th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL10-POSTGRESQLUPGRADE-19522104
  • published4 Sept 2026
  • disclosed13 Aug 2026

Introduced: 13 Aug 2026

NewCVE-2026-14666  (opens in a new tab)
CWE-524  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:10 postgresql-upgrade.

NVD Description

Note: Versions mentioned in the description apply only to the upstream postgresql-upgrade package and not the postgresql-upgrade package as distributed by RHEL. See How to fix? for RHEL:10 relevant fixed versions and status.

Incomplete tracking in PostgreSQL of changes to role membership, role attributes, and database ownership allows a query to continue using cached row-level security policies after those changes require a different policy, via plan reuse. Stale policies continue until some other event invalidates the cache or connection termination ends the session. This permits a user to complete reads and modifications that were recently permitted but now forbidden. An attacker must tailor an attack to a particular application's pattern of privilege removal and role-specific row security policies. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

CVSS Base Scores

version 3.1