# CVE-2026-5088: Apache::API::Password versions through 0.5.2 for Perl can generate insecure random values for salts

> An attacker can predict password salts due to insecure random generation, potentially facilitating password cracking attacks against systems using this Perl library.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Apr 2026
- **Updated:** 1 May 2026
- **Also known as:** GHSA-r6g6-6h6f-xcmj

## What is CVE-2026-5088?

CVE-2026-5088 is a high-severity vulnerability in JDEGUEST Apache::API::Password, published on 15 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG))

## Which versions are affected by CVE-2026-5088?

It affects 1 product.


Products: Jdeguest Apache\.

## How do I fix CVE-2026-5088?

No fix has been published for CVE-2026-5088 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-5088 being exploited?

There is no known exploitation of CVE-2026-5088 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-5088 and fix it if it is affected.

What it is: CVE-2026-5088 is a high-severity vulnerability in JDEGUEST Apache::API::Password, published on 15 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-5088 in the wild and no public exploit code.

Affected product: JDEGUEST Apache::API::Password. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-5088/ (Markdown: https://insights.sbomify.com/CVE-2026-5088/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-5088
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-5088
- OSV: https://osv.dev/vulnerability/CVE-2026-5088

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-5088/
Summaries are generated and may contain mistakes; the official description above is the record.