# CVE-2026-100293: Improper verification of cryptographic signature in Anjvision YSSD-RTMP-H5

> Attackers can install malicious firmware on Anjvision YSSD-RTMP-H5 devices because update mechanisms lack cryptographic signature verification.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-5v8p-59fw-m8g2

## What is CVE-2026-100293?

CVE-2026-100293 is a high-severity vulnerability in Anjvision YSSD-RTMP-H5, published on 29 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Anjvision YSSD‑RTMP‑H5 firmware version 3.3.2.4, both the local and cloud update mechanisms apply new firmware without any cryptographic verification, relying only on basic hashing. This design allows an attacker who can reach the update routine to introduce untrusted firmware images that the device will accept as valid.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

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


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

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

## Is CVE-2026-100293 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100293 is a high-severity vulnerability in Anjvision YSSD-RTMP-H5, published on 29 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-100293 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-100293/ (Markdown: https://insights.sbomify.com/CVE-2026-100293/index.md)
```

## Sources

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

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