CVE-2026-97469

Awaiting Analysis Awaiting Analysis - Queue

PostgreSQL Anonymizer Brute-Force Salt Disclosure

Publication date: 2026-09-25

Last updated on: 2026-09-29

Assigner: PostgreSQL

Description

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 masked role can run a RESTRICTED function when the call is placed inside the sub-select. The problem is resolved in PostgreSQL Anonymizer 3.2.3 and later versions

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-09-25

Last Modified

2026-09-29

Generated

2026-10-16

AI Q&A

2026-09-25

EPSS Evaluated

2026-10-14

NVD

CVE-2026-97469

EUVD

EUVD-2026-87134

Affected Vendors & Products

Vendor	Product	Version / Range
postgresql_anonymizer	postgresql_anonymizer	From 3.2.3 (inc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-328	The product uses an algorithm that produces a digest (output value) that does not meet security expectations for a hash function that allows an adversary to reasonably determine the original input (preimage attack), find another input that can produce the same hash (2nd preimage attack), or find multiple inputs that evaluate to the same hash (birthday attack).

Attack-Flow Graph

Executive Summary

PostgreSQL Anonymizer has a flaw where unprivileged masked users can repeatedly call the anon.hash() function. By collecting pairs of seed values and hash outputs, they can perform an offline brute-force attack to deduce the salt used for hashing.

Detection Guidance

To detect this vulnerability, check if PostgreSQL Anonymizer is running a version older than 3.2.3. Use commands like 'SELECT extversion FROM pg_extension WHERE extname = anon;' to verify the installed version. If the version is below 3.2.3, the system is vulnerable.

Impact Analysis

An attacker with access to the system could exploit this to recover original sensitive data from masked values, potentially exposing personal or confidential information that was intended to be anonymized.

Compliance Impact

This vulnerability could lead to unauthorized access to personal data, violating GDPR's data protection principles and HIPAA's requirements for safeguarding protected health information.

Mitigation Strategies

Upgrade PostgreSQL Anonymizer to version 3.2.3 or later to resolve the vulnerability. Review and restrict access to the anon.hash() function for masked users. Monitor for unusual activity involving repeated calls to the function.

Hi! I’m here to help you understand CVE-2026-97469. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70