Medium · CVSS 5.7CVE-2026-105617

PostgreSQL Anonymizer: Cached plans bypass transparent dynamic masking after a role change or a new masking ruleCVE-2026-105617

Answer in brief

CVE-2026-105617 records a Medium severity (CVSS 5.7) vulnerability in PostgreSQL Anonymizer: Cached plans bypass transparent dynamic masking after a role change or a new masking rule. The current sources do not mark it as known exploited. The current feed maps DALIBO/PostgreSQL Anonymizer (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 28, 2026Updated Oct 28, 2026Source checked Oct 28, 2026First seen by HOL Oct 28, 2026Material review Oct 28, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 5.7
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 5.7. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps DALIBO/PostgreSQL Anonymizer (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
DALIBO/PostgreSQL Anonymizergeneric	>=1 <3.3.0	3.3.0

Recommended response

Check inventory. Check lockfiles and deployed manifests for DALIBO/PostgreSQL Anonymizer.
Review the reported fix. Source-reported workaround: Disconnect active sessions after changing a masking rule.

Evidence timeline and material changes

Published upstream
Oct 28, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 28, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Oct 28, 2026

Sources and claim methodology

Source referencegitlab.com

Upstream source description

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.

Quoted source text, attributed separately from HOL analysis.