---
id: "CVE-2026-105619"
kind: "vulnerability"
aliases: ["CVE-2026-105619"]
title: "PostgreSQL Anonymizer: masking skipped for data read through security_invoker views"
severity: "medium"
cvss: 4.8
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["data-privacy", "package", "postgresql", "postgresql-anonymizer"]
not_affected_if: ["extension-not-installed", "no-security-invoker-views"]
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:08+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-105619", "first_seen_at": "2026-10-28T18:34:32+00:00"}]
---

# PostgreSQL Anonymizer: masking skipped for data read through security_invoker views

PostgreSQL Anonymizer does not apply its masking rules when data is read through a view created with security_invoker. A user querying such a view can see unmasked values that the masking policy was meant to hide.

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

## How to check

- Run `SELECT extversion FROM pg_extension WHERE extname = 'anon';` to get the installed PostgreSQL Anonymizer version
- Run `SELECT reloptions FROM pg_class WHERE relname = '<your_view_name>';` on views you expose to users, looking for `security_invoker=true`
- Confirm whether the database is actually using the anon masking rules on those views

## Fix

- Upgrade PostgreSQL Anonymizer to `3.3.0` or later
- Until upgraded, avoid exposing anonymized data through security_invoker views

## Timeline

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

## From the sources

PostgreSQL Anonymizer doesn't mask data accessed thru a security_invoker view. 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_