Cursor allows PostgreSQL Anonymizer masked user to gain unauthorized access to authentic data
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| DALIBO | PostgreSQL Anonymizer | unaffected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Dalibo | Postgresql Anonymizer | — |
Vendor Workaround
Disable dynamic masking
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-16928 | PostgreSQL Anonymizer v2.0 and v2.1 contain a vulnerability that allows a masked user to bypass the masking rules defined on a table and read the original data using a database cursor or the --insert option of pg_dump. This problem occurs only when dynamic masking is enabled, which is not the default setting. The problem is resolved in version 2.2.1 |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.364% probability within 30 days)
| Link | Providers |
|---|---|
| https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/531 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | PostgreSQL Anonymizer v2.0 and v2.1 contain a vulnerability that allows a masked user to bypass the masking rules defined on a table and read the original data using a database cursor or the --insert option of pg_dump. This problem occurs only when dynamic masking is enabled, which is not the default setting. The problem is resolved in version 2.2.1 | |
| Title | Cursor allows PostgreSQL Anonymizer masked user to gain unauthorized access to authentic data | |
| Weaknesses | CWE-200 | |
| References |
| |
| Metrics |
cvssV3_1
|