Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain local privileged access to camera
-
DeliverySupply tampered boot/firmware image
-
ExploitBypass Secure Boot signature verification (CWE-347)
-
ExecutionExecute unsigned boot code
-
ImpactFull device compromise and persistence
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Signature verification
|
| Exploitation Conditions | Exploitation requires local access to the Yoosee GM8135S Camera (CVSS AV:L - no network path) combined with high existing privileges on the device (PR:H), meaning the attacker must already be operating in a privileged context before abusing the Secure Boot signature-verification weakness. The specific feature affected is the device's Secure Boot cryptographic signature verification, which the exploit causes to improperly accept a manipulated image (CWE-347). Limiting factors for defenders: there is NO remote or unauthenticated path, no user-interaction-driven mass vector, and the capability is primarily useful for firmware tampering/persistence rather than initial access; the exact trigger mechanism is not described in the available sources. |
| Impact | This is a genuinely high-severity flaw (CVSS 4.0 base 8.4) but with meaningful real-world constraints that lower its operational urgency. The CVSS 4.0 vector is decisive on mechanism: AV:L means the attack must be approached locally (no network reach), and PR:H means the attacker already needs high privileges on the device before the flaw is useful. Those two factors together make this a post-compromise / supply-chain-tampering capability rather than a remotely-wormable issue. Against that, the impact metrics are maximal (VC:H/VI:H/VA:H plus subsequent-system SC:H/SI:H/SA:H), which fits a Secure Boot signature-verification bypass (CWE-347): defeating boot-chain trust undermines the integrity of the entire device. On the exploitation side the signals are modest and partly conflicting: the CVSS exploit-maturity is E:P (proof-of-concept), the multi-source data marks the PoC as 'reference only, not verified as working exploit code', there is NO CISA KEV listing, and no EPSS score was provided. The vendor was contacted but did not respond, so no fix is available. Net: a real priority for anyone deploying these specific cameras in sensitive settings, but the local-access + high-privilege precondition means it is not a mass-exploitation / drive-by threat. The vuln.today Decision label is 'this_week', consistent with elevated-but-not-emergency handling. |
| Exploit ScenarioDerived | An attacker with local, privileged access to a Yoosee GM8135S camera (for example via physical access, a service account, or a prior compromise) manipulates the device so that the Secure Boot stage improperly validates a cryptographic signature, allowing an unsigned or tampered firmware/boot image to be accepted. A public PoC reference exists (akosibrylle.me write-up), though it is not verified as working exploit code, so weaponization effort may still be required. Because the attack vector is local and requires high privileges, this is realistic as a persistence/tampering step rather than an initial remote intrusion. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Oct 26, 2026
Improper Secure Boot signature verification in Yoosee GM8135S Camera 21.00.01.36 lets a local attacker who already holds high privileges get a manipulated firmware image accepted (CWE-347), undermining firmware trust and enabling tampering or persistence. The CVSS 4.0 base score is 8.4, but the attack path is local and requires existing privileged access, with no remote or unauthenticated vector described; the exact trigger is not detailed in the available sources. A public PoC reference exists; it is not verified as working exploit code, and no CISA KEV entry confirms active exploitation; the disclosure is prioritized this_week.
Earlier versions of this analysis (1)
Secure Boot signature verification bypass in Yoosee GM8135S Camera firmware 21.00.01.36 allows a privileged local attacker to load an improperly signed boot or firmware image, compromising the confidentiality, integrity and availability of the device. Exploitation requires local access and high privileges (assessed CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H), so remote unauthenticated or mass exploitation is not indicated. A public PoC reference exists but is not verified as working exploit code; the vendor did not respond to disclosure, no fixed version is identified, and the issue is prioritized as act_now.
RemediationAI
No vendor-released patch or mitigation is identified at time of analysis; the description states the vendor did not respond to the disclosure. Compensating controls must focus on the prerequisite of local high privilege: restrict local and administrative access to the camera to trusted operators, secure any exposed debug, console, or firmware-update interfaces, and verify firmware images out-of-band before deployment; these reduce exposure but do not repair the signature-verification flaw and may be impractical where the camera must remain serviceable. If a signed-firmware-only or Secure Boot enforcement option is available, confirm it is enabled, though the reported issue is in that verification path. Network segmentation can limit post-exploitation reach but does not address the local Secure Boot bypass.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
CWE-347, Improper Verification of Cryptographic Signature, is the root-cause class: Secure Boot is supposed to validate a cryptographic signature over firmware before allowing it to run, but the affected verification logic can be manipulated to accept an image it should reject. The CPE cpe:2.3:a:yoosee:gm8135s_camera:*:*:*:*:*:*:*:* identifies the Yoosee GM8135S camera product line, and the report names version 21.00.01.36. Both the CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:H/UI:N) and the independent CVSS 3.1 assessment (AV:L/AC:L/PR:H/UI:N/S:C) agree that local access and high privileges are required; the sources do not describe the exact function or trigger, so the precise manipulation of the signature check is unverified. The CVSS 4.0 vector's E:P metric is consistent with a proof-of-concept reference, not with confirmed active exploitation.
Know when Gm8135S Camera gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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
Local access and high privileges are required to tamper with boot verification (AV:L/PR:H); defeating Secure Boot compromises components beyond the flawed one (S:C) with full C/I/A impact.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
Lifecycle Timeline
4DescriptionCVE.org
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.
Technical POC Analysis
CWE-347, Improper Verification of Cryptographic Signature, in the device boot chain of the Yoosee GM8135S camera (CWE-345, Insufficient Verification of Data Authenticity, in the researcher's own clas…
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
CVE-2026-116116 is a high-severity flaw in Yoosee GM8135S camera firmware that allows a local attacker with existing high privileges to install unauthorized firmware, compromising device trust. This affects physical security monitoring integrity, as manipulated firmware could enable persistence or surveillance tampering. Leadership should prioritize an upgrade plan and ensure no privileged access is left unmonitored.
No vendor-released patch identified at time of analysis. Interim mitigations include: strictly limiting administrative access to cameras, enforcing strong unique credentials, disabling remote firmware update interfaces if not needed, and monitoring device logs for unexpected firmware changes. Network segmentation to isolate cameras from critical systems reduces potential impact. A public PoC reference exists; it is not verified as working exploit code.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-109608
GHSA-8hgg-w6j7-2qjj
NVD
CVE.org
EPSS
VulDB
Exploit-DB