Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-13455: Use of Weak Hash in DALIBO PostgreSQL Anonymizer

0
Medium
VulnerabilityCVE-2026-13455cvecve-2026-13455
Published: 06/30/2026 (06/30/2026, 15:19:57 UTC)
Source: CVE Database V5
Vendor/Project: DALIBO
Product: PostgreSQL Anonymizer

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. The problem is resolved in PostgreSQL Anonymizer 3.1.2 and later versions

CVSS v3.1

Score 4.3medium

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Affected software

GitHub Actionsmore threats →ai
dalibo/postgresql_anonymizer
pkg:github/dalibo/postgresql_anonymizer
Affected versions
<3.1.2

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 06/30/2026, 16:23:04 UTC

Technical Analysis

The PostgreSQL Anonymizer product by DALIBO contains a weakness in its anon.hash() function where unprivileged masked users can repeatedly invoke the function to gather pairs of seeds and hash outputs. This data collection facilitates an offline brute-force attack aimed at deducing the salt value used in the hashing process. The vulnerability is addressed by updating to PostgreSQL Anonymizer version 3.1.2 or later.

Potential Impact

The vulnerability allows an attacker with limited privileges to perform offline brute-force attacks to recover the salt used in hashing, potentially weakening the anonymization process. The impact is limited to confidentiality (partial information disclosure) with no integrity or availability effects.

Mitigation Recommendations

Upgrade PostgreSQL Anonymizer to version 3.1.2 or later, where this vulnerability is resolved. No other mitigation or temporary fixes are documented.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
PostgreSQL
Date Reserved
2026-06-26T18:36:50.872Z
Cvss Version
3.1
State
PUBLISHED
Remediation Level
null

Threat ID: 6a43e61327e9c7971906ebee

Added to database: 06/30/2026, 15:51:47 UTC

Last enriched: 06/30/2026, 16:23:04 UTC

Last updated: 06/30/2026, 23:49:36 UTC

Views: 7

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses