CVE-2026-5088 affects Apache::API::Password in the Apache2-API Perl distribution through version 0.5.2. The vulnerability is in the _make_salt and _make_salt_bcrypt methods, which attempt to generate cryptographically secure random bytes for password salts by loading Crypt::URandom and then Bytes::Random::Secure. If neither module is available, the code falls back to generating 16 bytes using Perl's built-in rand function. Because rand is not suitable for cryptographic use, the resulting salts used in password hashing may be weak and predictable, reducing the security of stored password hashes.
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.
5 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.