---
id: "CVE-2026-105612"
kind: "vulnerability"
aliases: ["CVE-2026-105612"]
title: "PostgreSQL Anonymizer: data-modifying CTEs bypass read-only masked roles"
severity: "low"
cvss: 3.5
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["database", "package", "postgresql", "postgresql-anonymizer"]
not_affected_if: ["extension-not-installed", "no-masked-roles"]
published_at: "2026-10-28T18:17:02+00:00"
first_seen_at: "2026-10-28T18:34:32+00:00"
updated_at: "2026-10-28T18:35:16+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-105612", "first_seen_at": "2026-10-28T18:34:32+00:00"}]
---

# PostgreSQL Anonymizer: data-modifying CTEs bypass read-only masked roles

PostgreSQL Anonymizer lets data-modifying CTEs get past the read-only restriction placed on masked roles. An attacker with a masked role can write to data it was meant to only read.

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

## How to check

- Check the installed PostgreSQL Anonymizer version with `SELECT extversion FROM pg_extension WHERE extname = 'anonymizer';`
- Look for masked roles in your database that rely on read-only access to anonymized data.

## Fix

- Upgrade PostgreSQL Anonymizer to `3.3.0` or later.

## Timeline

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

## From the sources

PostgreSQL Anonymizer contains a vulnerability that data-modifying CTEs to bypass the read-only restriction of masked roles. 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_