Cyber Resilience

CVE-2026-5088

Jdeguest Apache\ \

Published
15 April 2026
Modified
06 May 2026
Patch / advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0057 44th percentile
Risk Priority 58 floored blend · peak EPSS

Summary

CVE-2026-5088 is a high-severity PRNG (CWE-338) vulnerability in Jdeguest Apache\. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Forge Web Credentials (T1606); ranked at the 44th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-13 (Cryptographic Protection) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-5088 affects Apache::API::Password, a Perl module within the Apache2-API distribution, in versions through 0.5.2. The vulnerability stems from the _make_salt and _make_salt_bcrypt methods, which attempt to generate cryptographically secure random bytes for password hashing salts by loading the Crypt::URandom or Bytes::Random::Secure modules. If both are unavailable, the methods fall back to Perl's built-in rand function to produce 16 bytes, which is unsuitable for cryptographic purposes due to its predictability (CWE-338: Use of Cryptographically Weak Pseudo-Random Number Generator). This results in weak salts for password hashing, with a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).

An attacker can exploit this vulnerability in environments where the affected module is used for password hashing without the required secure random modules installed. No privileges, user interaction, or special access are needed, and exploitation is feasible over a network if the application exposes hashed passwords (e.g., via database compromise or improper storage). Successful exploitation enables high-impact confidentiality loss, as predictable salts allow efficient offline cracking of password hashes through rainbow tables or targeted brute-force attacks, potentially exposing plaintext credentials.

Advisories recommend upgrading to Apache2-API version 0.5.3 or later, which addresses the fallback issue as noted in its release changes. Security guidance from metacpan.org emphasizes using cryptographically secure random sources like Crypt::URandom or Bytes::Random::Secure for all security-sensitive operations, with documentation available in module POD files and the metacpan security guide on random data. The issue was disclosed via the oss-security mailing list on 2026-04-15.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1606 Forge Web Credentials Credential Access
Adversaries may forge credential materials that can be used to gain access to web applications or Internet services.
T1606.001 Web Cookies Credential Access
Adversaries may forge web cookies that can be used to gain access to web applications or Internet services.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-26379Shared CWE-338
CVE-2024-58041Shared CWE-338
CVE-2024-45723Shared CWE-338
CVE-2023-24828Shared CWE-338
CVE-2023-28835Shared CWE-338
CVE-2026-46493Shared CWE-338
CVE-2024-23660Shared CWE-338
CVE-2026-25726Shared CWE-338
CVE-2024-56830Shared CWE-338
CVE-2023-31290Shared CWE-338

Affected Assets

jdeguest
apache\
\

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 3 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V7.2.3
  • V11.5.1

Mitigating Controls (NIST 800-53 r5) AI

Requiring specific approved cryptography for protection directly mandates use of strong PRNGs instead of weak ones.

Engineering principles applied during design and development include selection of cryptographically strong random number generation.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices explicitly require cryptographically strong RNG selection and usage in security contexts.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Mandates use of approved cryptographic controls, directly requiring cryptographically strong RNGs.

finds

Security testing can detect use of weak random number generators.

prevents

Secure SDLC processes should catch weak PRNG usage during design and code review.

prevents

Application security requirements can specify cryptographically strong random number generation.

prevents

Secure engineering principles include selection of appropriate cryptographic primitives.

prevents

Secure coding standards prohibit use of weak PRNGs in security contexts.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (1 rule)
  • V-248563 The OL 8 SSH server must be configured to use strong entropy. prevents CWE-338
RHEL 8 (1 rule)
  • V-230253 RHEL 8 must ensure the SSH server uses strong entropy. prevents CWE-338
Ubuntu 22.04 (1 rule)
  • V-260650 Ubuntu 22.04 LTS must implement NIST FIPS-validated cryptography to protect classified information and for the following: To provision digital signatures, to generate cryptographic hashes, and to protect unclassified information requiring confidentiality and cryptographic protection in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. prevents CWE-338

References