DALIBO has 16 CVEs on record. Disclosure cadence is accelerating: 16 in the last 90 days against 0 in the 90 before. The busiest recent month was October 2026 with 12. The median CVSS is 5.3 (medium). None have a confirmed exploitation report. The most common weakness class is CWE-862 (4).
CVEs per month
Last 12 months, by publish date
- Exploited share
- 0% vs 1% corpus
- Median CVSS
- 5.3
- Publish → KEV
- —
- Last 90 days
- 16 prev 0
Worst active — by depth score
CVE-2026-19633High· 8.8PostgreSQL Anonymizer contains a vulnerability that allows unprivileged masked users to execute arbitrary code by abusing operators, domain casts, or view subqueries that carry untrusted expressions49CVE-2026-110181Medium· 6.5PostgreSQL Anonymizer: Function declared with SQL-standard syntax leak anonymized data36CVE-2026-105620Medium· 6.5PostgreSQL Anonymizer: A masked role reads the authentic data of masked tables through a masking rule with a sub-query36CVE-2026-83534Medium· 6.4PostgreSQL Anonymizer contains a vulnerability in the anon.anonymize_database_parallel() function that allows the owner of a table to run arbitrary code with superuser privilege35CVE-2026-19634Medium· 6.4PostgreSQL Anonymizer contains a SQL injection vulnerability in two import functions35
DALIBO vulnerabilities
CVEs affecting DALIBO, newest first. Open any entry for full detail, references, and exploit status.
16 CVEsRSS
CVE-2026-105614Medium· 4.7PostgreSQL Anonymizer: Unbounded image-decode memory allocation (DoS) in anon.image_blur()
PostgreSQL Anonymizer's `anon.image_blur()` function doesn't check the declared dimension of the provided image, allowing an attacker to provide a small image with enormous declared dimensions. This vulnerability can be exploited to exha…
CVE-2026-105612Low· 3.5PostgreSQL Anonymizer: Data-modifying CTEs bypass the read-only restriction of masked roles
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
CVE-2026-110181Medium· 6.5PostgreSQL Anonymizer: Function declared with SQL-standard syntax leak anonymized data
PostgreSQL Anonymizer contains a vulnerability related to anonymization functions defined using SQL-standard function bodies. PostgreSQL analyses such functions at declaration time, while Anonymizer only attempts to check them at executi…
CVE-2026-105616Medium· 5.7PostgreSQL Anonymizer: The secret salt and shift of anon are readable by any role in pg_roles or pg_db_role_setting
PostgreSQL restricts acces to the salt and shift via the `SHOW` command for users not member of `pg_read_all_settings`. But they are visible in `pg_db_role_setting` or `pg_roles` if they were set on the database, user or both. PostgreSQL…
CVE-2026-105620Medium· 6.5PostgreSQL Anonymizer: A masked role reads the authentic data of masked tables through a masking rule with a sub-query
PostgreSQL Anonymizer doesn't mask data returned by a sub-query in a rule. The problem is resolved in PostgreSQL Anonymizer 3.3.0 and later versions.
CVE-2026-105618Medium· 5.7PostgreSQL Anonymizer: Masked partitions and child tables are not masked when they are queried through their parent
PostgreSQL Anonymizer's documentation recommends applying rules on partitions and inheritance tables. Direct access to the paritions / inheritance tables is masked but not thru the parent table. The problem is resolved in PostgreSQL Anon…
CVE-2026-110183Medium· 4.3PostgreSQL Anonymizer: statistics can expose some of the original data after statistic masking
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 manua…
CVE-2026-105613Medium· 4.7PostgreSQL Anonymizer: Unbounded memory allocation (DoS) in range-based dummy functions
PostgreSQL Anonymizer's range-based dummy functions dont constraint the range size. This vulnerability can be exploited to exhaust the memory of a backend and OOM-kill it (when ovecommit is on), which results in a cluster-wide crash reco…
CVE-2026-105617Medium· 5.7PostgreSQL Anonymizer: Cached plans bypass transparent dynamic masking after a role change or a new masking rule
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…
CVE-2026-105615Low· 3.5PostgreSQL Anonymizer: Masked roles can read the statistics of masked columns in pg_stats
PostgreSQL's optimized statistics on a table are visible as long as you have SELECT privilege on said table. A masked role can therefore read a limited subset of the data through the statistics view's histograms and mcvs. The vulnerabili…
CVE-2026-105619Medium· 4.8PostgreSQL Anonymizer: Masking rules of the tables are not applied through security_invoker views
PostgreSQL Anonymizer doesn't mask data accessed thru a security_invoker view. The problem is resolved in PostgreSQL Anonymizer 3.3.0 and later versions.
CVE-2026-110182Medium· 4.3PostgreSQL Anonymizer: anon.partial() and anon.partial_email() can reveal the whole data
PostgreSQL Anonymizer contains a vulnerability related to the anon.partial() and anon.partial_email() functions. These function can reveal the while data if the data is small enough. The issue is fixed in PostgreSQL Anonymizer 3.3.0 and …
CVE-2026-97469Medium· 4.3PostgreSQL Anonymizer contains a vulnerability that allows unprivileged masked users to repeatedly call the anon.hash() function and collects (seed, hash_output) pairs to perform an offline brute-force attack and deduce the salt
PostgreSQL Anonymizer contains a vulnerability that allows unprivileged masked users to repeatedly call the anon.hash() function and collects (seed, hash_output) pairs to perform an offline brute-force attack and deduce the salt. A maske…
CVE-2026-83534Medium· 6.4PostgreSQL Anonymizer contains a vulnerability in the anon.anonymize_database_parallel() function that allows the owner of a table to run arbitrary code with superuser privilege
PostgreSQL Anonymizer contains a vulnerability in the anon.anonymize_database_parallel() function that allows the owner of a table to run arbitrary code with superuser privilege. The issue is fixed in PostgreSQL Anonymizer 3.2.0 and late…
CVE-2026-19634Medium· 6.4PostgreSQL Anonymizer contains a SQL injection vulnerability in two import functions
PostgreSQL Anonymizer contains a SQL injection vulnerability in two import functions. A user can create a malicious JSON document containing specially crafted object names. If a superuser subsequently calls anon.import_database_rules() o…
CVE-2026-19633High· 8.8PostgreSQL Anonymizer contains a vulnerability that allows unprivileged masked users to execute arbitrary code by abusing operators, domain casts, or view subqueries that carry untrusted expressions
PostgreSQL Anonymizer contains a vulnerability that allows unprivileged masked users to execute arbitrary code by abusing operators, domain casts, or view subqueries that carry untrusted expressions. When these objects are evaluated in t…