CVE-2026-97469 DALIBO CVE debrief

Who should care

Defenders responsible for systems using PostgreSQL Anonymizer, especially those with unprivileged users, should assess exposure and prioritize verification and potential upgrades. This includes operators, platform administrators, vulnerability management teams, and security teams who need to evaluate the impact on their systems and take appropriate actions to mitigate the vulnerability.

Why it matters

CVE-2026-97469 allows unprivileged users in PostgreSQL Anonymizer to perform offline brute-force attacks, requiring defenders to verify exposure and prioritize upgrades.

• Potential offline brute-force attacks against the salt used in PostgreSQL Anonymizer
• Need to verify exposure and assess impact on systems using vulnerable versions
• Possible data security risks if an attacker can deduce the salt

Technical summary

The vulnerability in PostgreSQL Anonymizer allows unprivileged masked users to repeatedly call the anon.hash() function and collect (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. This issue is resolved in PostgreSQL Anonymizer 3.2.3 and later versions. The vulnerability impacts systems using PostgreSQL Anonymizer versions prior to 3.2.3, requiring defenders to verify exposure and prioritize upgrades.

Defensive priority

Defenders should prioritize verifying exposure and assessing the impact of this vulnerability on their systems, especially those using PostgreSQL Anonymizer versions prior to 3.2.3.

Recommended defensive actions

• Verify the version of PostgreSQL Anonymizer in use and assess exposure
• Upgrade to PostgreSQL Anonymizer 3.2.3 or later if vulnerable
• Monitor for suspicious activity related to the anon.hash() function
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but the scope of affected systems and potential impact require further verification. Defenders should verify the version of PostgreSQL Anonymizer in use, assess exposure, and monitor for suspicious activity related to the anon.hash() function. The vulnerability's impact on systems using vulnerable versions needs careful evaluation, considering the potential for offline brute-force attacks against the salt used in PostgreSQL Anonymizer.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.