Analysis and contextual insights are available on OpenCVE Cloud.
Vendor Workaround
Run the ANALYZE command after static masking.
Tracking
Sign in to view the affected projects.
No advisories yet.
| Link | Providers |
|---|---|
| https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/722 |
|
Wed, 28 Oct 2026 19:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Dalibo
Dalibo postgresql Anonymizer |
|
| Vendors & Products |
Dalibo
Dalibo postgresql Anonymizer |
Wed, 28 Oct 2026 17:45:00 +0000
| 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
|
Status: PUBLISHED
Assigner: PostgreSQL
Published:
Updated: 2026-10-28T17:31:53.824Z
Reserved: 2026-10-13T17:14:55.395Z
Link: CVE-2026-110183
No data.
Status : Received
Published: 2026-10-28T18:17:05.710
Modified: 2026-10-28T18:17:05.710
Link: CVE-2026-110183
No data.
OpenCVE Enrichment
Updated: 2026-10-28T18:45:06Z
-
CWE-202
Exposure of Sensitive Information Through Data Queries