---
id: "CVE-2026-105617"
kind: "vulnerability"
aliases: ["CVE-2026-105617"]
title: "PostgreSQL Anonymizer: cached plans keep showing unmasked data after rule changes"
severity: "medium"
cvss: 6.5
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["package", "postgresql", "postgresql-anonymizer", "self-hosted"]
not_affected_if: ["default-config"]
published_at: "2026-10-28T18:17:03+00:00"
first_seen_at: "2026-10-28T18:34:32+00:00"
updated_at: "2026-10-28T18:35:03+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-105617", "first_seen_at": "2026-10-28T18:34:32+00:00"}]
---

# PostgreSQL Anonymizer: cached plans keep showing unmasked data after rule changes

PostgreSQL Anonymizer does not invalidate query plans prepared after a masking rule was added or a role was changed. A user with such a prepared plan can keep seeing unmasked data until the session ends.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed extension version with `SELECT extversion FROM pg_extension WHERE extname = 'anon';`
- Look for long-lived sessions or connection pools that prepare statements against masked tables

## Fix

- Upgrade PostgreSQL Anonymizer to `3.3.0` or later
- Reconnect sessions (or restart the pool) after upgrading so old prepared plans are discarded

## Timeline

- 2026-10-28T18:34:32+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-105617

## From the sources

PostgreSQL Anonymizer doesn't invalidate plans prepared after a rule was added or a role changed. Users using such plans can still see the unmasked data until the end of the session. The problem is resolved in PostgreSQL Anonymizer 3.3.0 and later versions.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_