# CVE-2026-86187: WWBN AVideo Weak PRNG Password Generation via External Login

> Attackers can recover plaintext passwords for external-login accounts via offline brute-force due to weak PRNG and unsalted hashing, leading to account takeover.

- **Severity:** High 7.4 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Sep 2026
- **Updated:** 10 Sep 2026
- **Also known as:** GHSA-h3ff-c2qq-pr2g, GHSA-hfr9-8xm8-cq6w

## What is CVE-2026-86187?

CVE-2026-86187 is a high-severity vulnerability in WWBN AVideo, published on 5 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

WWBN AVideo generates passwords for external-login accounts using rand() instead of a cryptographic generator, producing only 31-bit integers. Attackers with access to password hashes can recover plaintext passwords in minutes through offline brute-force attacks due to unsalted MD5-based hashing.

Weakness: CWE-330 (Use of Insufficiently Random Values)

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


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

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

## Is CVE-2026-86187 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86187 is a high-severity vulnerability in WWBN AVideo, published on 5 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-86187 in the wild and no public exploit code.

Affected product: WWBN AVideo. 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-86187/ (Markdown: https://insights.sbomify.com/CVE-2026-86187/index.md)
```

## Sources

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

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