CVE-2026-5088 json
Apache::API::Password versions through 0.5.2 for Perl can generate insecure random values for salts
published 2026-04-15 6 mo ago modified 2026-10-26 13 d ago also EUVD-2026-22840
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 47%
- public exploits
- 0
- none known
Summary
Apache::API::Password versions through 0.5.2 for Perl can generate insecure random values for salts.
The _make_salt and _make_salt_bcrypt methods will attept to load Crypt::URandom and then Bytes::Random::Secure to generate random bytes for the salt. If those modules are unavailable, it will simply return 16 bytes generated with Perl's built-in rand function.
The rand function is unsuitable for cryptographic use.
These salts are used for password hashing.
Patch / fix
- jdeguest apache::api::password 0.5.3
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 6 mo ago
Exploit prediction
0.57% chance of exploitation in the next 30 days, higher than 47% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected products
- JDEGUEST Apache::API::Password
Classification
- Weakness
-
- CWE-338 Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
References
-
metacpan.org
/release/JDEGUEST/Apache2-API-v0.5.3/changes
release-notes
-
metacpan.org
/release/JDEGUEST/Apache2-API-v0.5.2/view/lib/Apache2/API/Password.pod
related, product
-
security.metacpan.org
/docs/guides/random-data-for-security.html
technical-description, product
-
metacpan.org
/pod/Crypt::URandom
product
-
openwall.com
/lists/oss-security/2026/04/15/4
mailing-list, third-party-advisory
-
openwall.com
/lists/oss-security/2026/04/15/5
mailing-list, third-party-advisory
Sources
- CVE List CVE-2026-5088
- NVD CVE-2026-5088
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.