Live › vulnerability › CVE-2026-110182
Go to dashboardThe anon.partial() and anon.partial_email() functions in PostgreSQL Anonymizer can expose the full original value when that value is short. An attacker who can read the masked output recovers data the masking was meant to hide.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 18:34 UTC. All times on this page are UTC.
Teams that use PostgreSQL Anonymizer to mask data with anon.partial() or anon.partial_email() on short fields such as names, codes or small identifiers. Systems that do not use these two functions, or that only mask long free-text values, are unlikely to be exposed.
No product ranges from the sources yet.
SELECT extversion FROM pg_extension WHERE extname = 'anon'; and compare it to 3.3.0anon.partial( and anon.partial_email( on short fields3.3.0 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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 later versions.
This page as .md · .json · in your agent: get_signal("CVE-2026-110182")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.