Live › vulnerability › CVE-2026-105618
Go to dashboardPostgreSQL Anonymizer's documentation recommends applying masking rules to partitions and inheritance tables. Querying the parent table does not apply the masking, so data reached through it is exposed unmasked.
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 using PostgreSQL Anonymizer to mask data in databases that use partitioned tables or table inheritance, where the masking rules are applied to the child tables. Exposure depends on users reading the data through the parent table. Teams not using the extension, or not using partitions or inheritance, can skip it.
No product ranges from the sources yet.
SELECT extversion FROM pg_extension WHERE extname = 'anonymizer';)anon configuration3.3.0 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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 Anonymizer 3.3.0 and later versions.
This page as .md · .json · in your agent: get_signal("CVE-2026-105618")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.