Public vulnerability disclosure

CVE-2026-110181

PostgreSQL Anonymizer: Function declared with SQL-standard syntax leak anonymized data

publishedCWE-693

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 execution time. This problem can be exploited by any user with the TEMPORARY privilege. The issue is fixed in PostgreSQL Anonymizer 3.3.0 and later versions.

Technical severity6.5 mediumCVSS 3.1 · CNA: PostgreSQL
Published2026-10-28Source updated 2026-11-05
Collected2026-11-053 attributed sources

Fixes and workarounds

Workaround

Revoke TEMPORARY from PUBLIC and CREATE on all schemas from masked roles to prevent them from creating a function. Revoke EXECUTE from PUBLIC on function with SQL-standard bodies since anon fails to anonymize the data they return.

Source: CNA: PostgreSQL

Affected products and versions

Affected products, source version ranges and reporting authorities
ProductVersionsAuthority
PostgreSQL Anonymizer
DALIBO
≥ 1; < 3.3.0 (affected, semver)
Other versions: unaffected
CNA: PostgreSQL

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

CVSS scores, vectors and reporting authorities
Version / scoreVectorAuthority
3.1 / 6.5
medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NCNA: PostgreSQL
3.1 / 6.5
medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NNVD: f86ef6dc-4d3a-42ad-8f28-e6d5547a5007

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide