Improper WiFi initialization in Yoosee GM8135S Camera

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-116115?

CVE-2026-116115 is a vulnerability classified as Improper Initialization, affecting GM8135S Camera (affected versions: 21.00.01.36). This vulnerability is rated Low, with a CVSS score of 2.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 security vulnerability has been detected in Yoosee GM8135S Camera 21.00.01.36. This impacts an unknown function of the file wpa_supplicantX.conf of the component WiFi Configuration. Such manipulation leads to improper initialization. The attack can only be initiated within the local network. This attack is characterized by high complexity. The exploitability is said to be difficult. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Affected products and scope

  • Confirmed affected: Yoosee GM8135S Camera version 21.00.01.36. The relevant component is WiFi Configuration and the associated file is wpa_supplicantX.conf.
  • Fix status: No fixed release or remediating firmware is confirmed in the record or the reviewed sources.
  • Unverified scope: The public writeup describes versions up to and including 21.00.01.36, while leaving open the possibility of additional versions. The CVE record confirms only 21.00.01.36; later or parallel branches must not be treated as unaffected without separate verification.

Technical details

The vulnerability is in the WiFi Configuration component and involves handling of wpa_supplicantX.conf. The record identifies an unknown function and states that manipulation of an unspecified input can cause improper initialization, classified as CWE-665. An attacker must be present on the local or adjacent network, does not need authentication, and does not require user interaction, but exploitation is highly complex. The record does not identify the parameter, input format, network interface, or exact implementation detail that produces the incorrect initialization state. A public PoC writeup describes the device automatically connecting to several passwordless default WiFi SSIDs; the full relationship between those broader behaviors and this CVE is not established, so they should be treated as a possible deployment risk rather than a confirmed direct consequence.

Exploitability

The vulnerability can be initiated from the local or adjacent network. The record states that authentication and user interaction are not required, while attack complexity is high and exploitability is described as difficult. The exploit has been publicly disclosed and a public proof of concept is available; VulDB also labels the exploitation status as Proof-of-Concept. The public writeup demonstrates network observation and WiFi association behavior, but the available evidence does not establish exploitation in deployed environments. The current evidence is insufficient to determine whether the vulnerability is being actively exploited in the wild.

Technical impact

The confirmed technical outcome is improper initialization in the WiFi Configuration component, primarily affecting the integrity of the WiFi state or configuration handling. The record does not establish a direct confidentiality or availability impact, code execution, or privilege escalation. Exploitation requires local-network reachability, does not require an account or user interaction, and is technically difficult. Organisationally, cameras may become untrusted monitoring endpoints that require segmentation, replacement, or additional review. The public writeup describes possible privacy exposure from unencrypted UDP video and automatic WiFi association, but those behaviors have not been fully isolated as direct impacts of this CVE.

Business impact

The camera may initialize an incorrect WiFi state, reducing confidence in its network connection and configuration integrity. In homes, offices, or sensitive monitoring environments, altered connection behavior could cause a camera to associate with unapproved WiFi infrastructure if the default configurations described in the public writeup remain present. That writeup also describes potential exposure of live video transmitted without encryption under specific conditions; this is a possible deployment-level risk and should not be treated as a confirmed direct impact of this CVE alone. The available evidence does not show that the flaw by itself causes broad data loss, service disruption, or device takeover. The absence of an identified vendor fix increases the operational cost of isolating, replacing, and monitoring affected devices.

Remediation

  1. Identify and isolate affected devices: Inventory Yoosee GM8135S Camera deployments and treat every device running 21.00.01.36 as potentially affected.
  2. Do not assume a patch exists: No remediating firmware is identified. Monitor official vendor communications and verify each release branch independently; do not infer that a later version is fixed without supporting evidence.
  3. Reduce network exposure: Place cameras on a dedicated IoT VLAN, prevent direct routing to trusted networks, and apply strict firewall rules, especially for outbound Internet traffic. This mitigation comes from the public writeup and is not a vendor-confirmed fix.
  4. Reduce rogue WiFi association risk: Use Ethernet where feasible to limit the possibility that the device is forced off its current WiFi network and automatically joins an unapproved network.
  5. Protect remote viewing: If remote viewing is required, prefer routing the local RTSP stream through a self-hosted NVR or reverse proxy that enforces TLS instead of exposing vulnerable P2P infrastructure directly.
  6. Replace when isolation is not possible: If adequate network segmentation and egress control cannot be implemented, replace the device with one that requires transport-layer encryption by default.

Detection

  1. Inventory all Yoosee GM8135S Camera devices and firmware versions, prioritizing devices running 21.00.01.36.
  2. Where administrative or forensic access is available, inspect wpa_supplicantX.conf and related WiFi configuration files. Check for default open SSIDs such as Free-AP0, Free-AP1, Free-AP2, and Free-AP3.
  3. Review wireless controller, access point, and DHCP logs for the camera associating with unapproved SSIDs, unexpected access-point changes, or reconnecting after deauthentication events. Treat this as precautionary monitoring, not as a confirmed CVE-specific IOC.
  4. During an active live stream, inspect network captures for unencrypted UDP video or unexpected outbound camera traffic. The public writeup demonstrates this type of traffic, but it does not establish that every similar flow is specific to this CVE.
  5. The absence of these signs does not prove that a device is safe or 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.