Yoosee GM8135S Camera Improperly Verifies Cryptographic Signatures in Secure Boot

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2026-116116?

CVE-2026-116116 is a vulnerability classified as Improper Verification of Cryptographic Signature and Insufficient Verification of Data Authenticity, affecting GM8135S Camera (affected versions: 21.00.01.36). This vulnerability is rated Critical, with a CVSS score of 9.3. Public exploit code or evidence is available for this vulnerability, but that does not confirm exploitation in the wild.

Overview

Original source data

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.

Affected products and scope

  • Yoosee GM8135S Camera: version 21.00.01.36 is affected.
  • Component: Secure Boot.
  • No fixed release, affected parallel branch, or default-status qualifier is supplied. The status of versions other than 21.00.01.36 is unknown.

Technical details

The affected component is Secure Boot, but the exact function is not identified. The weakness is classified as CWE-347, Improper Verification of Cryptographic Signature, and CWE-345, Insufficient Verification of Data Authenticity. The record describes manipulation of an unspecified input or behavior that causes cryptographic signature verification to be performed incorrectly. The attacker-controlled input, boot stage, signature format, and vulnerable code path remain unknown. Reachability is local, remote access is not reported, high privileges are required, and no user interaction is required. The available evidence identifies a public proof of concept but does not provide a reproducible attack sequence.

Exploitability

  • Reachability: The CNA entry marks the attack as local and not remote; partial physical access is also noted.
  • Prerequisites: High privileges are required, and user interaction is not required. The reported attack complexity is low.
  • Public status: A public proof of concept is reported. The supplied evidence does not confirm exploitation in the wild, a named campaign, or a specific victim.
  • Disclosure limitation: Exact exploit steps and the affected implementation detail are not public in the reviewed evidence.

Technical impact

Successful exploitation could undermine the camera's boot trust boundary by allowing data or software with an improperly verified signature to pass a security check. The stated outcome can affect confidentiality, integrity, and availability, so a compromised device could potentially expose camera data, permit unauthorized modification, or become unavailable. The attack is local and requires high privileges, which limits reachability compared with a remotely exploitable flaw. The record does not establish persistence, impact on other devices, or an actual compromise.

Business impact

The principal risk is loss of trust in the camera's boot chain. If exploitation succeeds, an attacker may cause the device to accept improperly authenticated software or data, which could lead to unauthorized changes, exposure of camera-related information, or loss of service. These are potential consequences consistent with the reported confidentiality, integrity, and availability impact, not a confirmed breach scenario. The available evidence does not identify a victim, campaign, or specific organizational compromise.

Remediation

  1. Replace or remove affected devices where feasible. The CNA advisory states that no countermeasure is known and suggests using an alternative product.
  2. Do not assume that an unlisted firmware release fixes the issue. No fixed release is supplied, and no vendor mitigation is confirmed.
  3. As a precaution, restrict local and physical administrative access to affected cameras and place them in a controlled deployment area until a vendor-supported fix is available. This reduces the stated access prerequisite but does not repair the boot-verification defect.
  4. Reassess the device before redeployment when the vendor publishes a firmware update or corrective advisory, and verify that it explicitly addresses Secure Boot signature verification.

Detection

  1. Inventory Yoosee devices by model and firmware version, and flag GM8135S Camera running 21.00.01.36.
  2. Confirm whether Secure Boot is present and record any vendor-provided Secure Boot status or verification result. The record supplies no named log event or indicator, so do not treat the absence of such evidence as proof of safety.
  3. Review local administrative and maintenance access, including physical access, for affected devices. This is a precaution based on the local, high-privilege attack prerequisites, not a known IOC.
  4. If replacement firmware is offered, validate the exact affected branch and the vendor's statement about signature verification before treating the device as remediated.
Sources (21)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.