# CVE-2026-116116: Yoosee GM8135S Camera Secure Boot signature verification


- **Severity:** Critical 9.3 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-8hgg-w6j7-2qjj

## What is CVE-2026-116116?

CVE-2026-116116 is a critical vulnerability in Yoosee GM8135S Camera, published on 26 Oct 2026. 

### Official description

A vulnerability was detected in Yoosee GM8135S Camera 21.00.01.36. Affected is an unknown function of the component Secure Boot. Performing a manipulation results in improper verification of cryptographic signature. The attack needs to be approached locally. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature), CWE-345 (Insufficient Verification of Data Authenticity)

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


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

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

## Is CVE-2026-116116 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116116 is a critical vulnerability in Yoosee GM8135S Camera, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116116 in the wild and no public exploit code.

Affected product: Yoosee GM8135S Camera. 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-116116/ (Markdown: https://insights.sbomify.com/CVE-2026-116116/index.md)
```

## Sources

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

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