Loading vulnerability…
A timing side-channel vulnerability in PostgreSQL authentication allows recovery of credentials when the server compares MD5-hashed passwords using non-timing-safe comparison logic. The issue affects deployments that still use legacy MD5 password authentication, including databases whose password hashes originated from upgrades from PostgreSQL 13 or earlier. SCRAM-SHA-256 passwords are not affected. PostgreSQL addressed the issue by replacing non-timing-safe password and hash comparisons in authentication code with timing-safe comparison routines. Affected versions are PostgreSQL releases before 18.4, 17.10, 16.14, 15.18, and 14.23.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
29 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability in PostgreSQL addressed indirectly through upgraded third-party components in Tenable Security Center.
A PostgreSQL vulnerability involving an MD5 credential timing leak.
A PostgreSQL authentication hardening issue involving non-timing-safe string comparisons for passwords and hashes, with uncertain practical exploitability.
A PostgreSQL authentication-side timing issue caused by non-timing-safe string comparisons when checking passwords and hashes.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.