CVE-2026-110183

PostgreSQL Anonymizer: statistics can expose some of the original data after statistic masking

Published Oct 28, 2026 CVSS 3.1 · 4.3 Medium EPSS < 1% KEV · Not listed
Description
PostgreSQL Anonymizer contains a vulnerability related to static masking and statistics persistence. Statistics pertaining to the original data remain visible in pg_stats until an ANALYZE operation is performed on the table, either manually or by autovacuum. This issue is fixed in PostgreSQL Anonymizer 3.3.0 and later versions.

Analysis

AI-generated

Technical impact

PostgreSQL Anonymizer implements static masking of sensitive data, but the statistics that the database engine collects on the underlying columns can still contain information about the original values. Once data is masked, statistics are retained in the pg_stats catalog until an ANALYZE operation runs on the affected table. Until that moment, the statistics can expose a subset of the original data, potentially revealing patterns or specific values that were intended to be hidden.

Affected Systems

The vulnerability affects all versions of the PostgreSQL Anonymizer plugin supplied by DALIBO that were released before version 3.3.0. The fix was introduced in 3.3.0 and later releases, which remove the retained statistics or require a fresh analyze after masking.

Risk and Exploitability

The CVSS score of 4.3 indicates moderate severity, largely due to the information‑disclosure nature of the flaw. The EPSS score is not available, and the vulnerability has no record in the CISA KEV catalog. Exploitation requires a user with sufficient privileges to invoke an ANALYZE operation or trigger an autovacuum that performs analyze on the masked tables. Because of the privilege requirement and the lack of a remote exploitation vector, the overall risk to systems is moderate but warrants timely remediation.

Remediation

Vendor Workaround

Run the ANALYZE command after static masking.


OpenCVE Recommended Actions

  • Upgrade PostgreSQL Anonymizer to version 3.3.0 or newer, which eliminates the statistics leakage.
  • If an upgrade is not possible immediately, run the ANALYZE command on any masked tables to purge the old statistics from pg_stats.
  • Configure autovacuum or add a manual trigger to ensure that ANALYZE runs after masking the data to prevent future leaks.

Generated by OpenCVE AI on October 28, 2026 at 18:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:dalibo:postgresql_anonymizer:*:*:*:*:*:postgresql:*:*
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Dalibo
Dalibo postgresql Anonymizer
Vendors & Products Dalibo
Dalibo postgresql Anonymizer
Type Values Removed Values Added
Description PostgreSQL Anonymizer contains a vulnerability related to static masking and statistics persistence. Statistics pertaining to the original data remain visible in pg_stats until an ANALYZE operation is performed on the table, either manually or by autovacuum. This issue is fixed in PostgreSQL Anonymizer 3.3.0 and later versions.
Title PostgreSQL Anonymizer: statistics can expose some of the original data after statistic masking
Weaknesses CWE-202
References
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N'}

Weaknesses
  • CWE-202

    Exposure of Sensitive Information Through Data Queries

Sources

Status
PUBLISHED
Assigner
PostgreSQL
Published
Updated
Nov 5, 2026, 4:51 PM
Reserved
Oct 13, 2026, 5:14 PM
Status
Analyzed
Published
Oct 28, 2026, 6:17 PM
Modified
Nov 12, 2026, 8:51 PM