# CVE-2026-100299: Use of Weak Credentials in Anjvision YSSD-RTMP-H5

> Attackers can exploit weak DES-based password hashes on the serial console to bypass authentication and gain privileged access to the device.

- **Severity:** High 7.0 (`CVSS:4.0/AV:P/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-mv5g-v6hm-qrrg

## What is CVE-2026-100299?

CVE-2026-100299 is a high-severity vulnerability in Anjvision YSSD-RTMP-H5, published on 29 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In Anjvision YSSD‑RTMP‑H5 firmware version 3.3.2.4, the device includes a legacy password hash on the serial console that relies on a weak DES‑based encryption.

Weakness: CWE-1391 (Use of Weak Credentials)

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


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

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

## Is CVE-2026-100299 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100299 is a high-severity vulnerability in Anjvision YSSD-RTMP-H5, published on 29 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-100299 in the wild and no public exploit code.

Affected product: Anjvision YSSD-RTMP-H5. 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-100299/ (Markdown: https://insights.sbomify.com/CVE-2026-100299/index.md)
```

## Sources

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

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