CVE-2026-36933: Arbitrary Code Execution in Boyleep K11 y108 Factory Test Feature
Boyleep K11 y108 devices running firmware version 2.3.0.11291 contain a vulnerability in their factory test feature that allows an attacker with physical access to execute arbitrary code. This means someone with hands-on access to the device can bypass normal security controls and run malicious code with full device privileges. The vulnerability requires no special permissions or user interaction to exploit once physical access is achieved.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 6.8 MEDIUM · CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Weaknesses (CWE)
- CWE-284
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-06-15 / 2026-06-17
NVD description (verbatim)
An issue in Boyleep K11, y108 firmware v.2.3.0.11291 allows a physically proximate attacker to execute arbitrary code via the factory test feature.
1 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-36933 is an improper access control vulnerability (CWE-284) in the Boyleep K11 y108 firmware 2.3.0.11291 that exposes a factory test interface without adequate authentication or authorization mechanisms. An attacker with physical proximity can invoke this test feature to execute arbitrary code at the device level. The attack vector is physical (AV:P), requires no privileges (PR:N), is straightforward to execute (AC:L), and does not require user interaction (UI:N). Impact spans confidentiality, integrity, and availability of the device.
Business impact
Organizations deploying Boyleep K11 y108 devices must assess whether these devices operate in physically secure environments. In settings where devices may be accessed by untrusted individuals—such as public kiosks, retail locations, or field-deployed hardware—this vulnerability enables complete device compromise. Attackers could exfiltrate sensitive data stored on the device, modify its behavior, disable it, or use it as an entry point into a broader network. The risk is directly proportional to the threat model of your deployment environment.
Affected systems
This vulnerability specifically affects Boyleep K11 y108 devices with firmware version 2.3.0.11291. Organizations should inventory all instances of this device model and firmware version in their environment. Check device management systems, procurement records, and active deployments. Firmware version details should be verified through the device web interface, CLI, or management platform used in your environment.
Exploitability
Exploitation requires physical access to the device, which significantly reduces the practical attack surface compared to remote vulnerabilities. However, CVSS score of 6.8 (MEDIUM) reflects the high impact once access is achieved. The attack is not complex and requires no special knowledge beyond accessing the factory test feature. This vulnerability does not currently appear on CISA's Known Exploited Vulnerabilities (KEV) catalog, suggesting no active widespread exploitation has been publicly documented. Nevertheless, physical access exploits are inherently difficult to detect and may be executed without leaving traces.
Remediation
Firmware updates should be prioritized for all Boyleep K11 y108 devices. Verify the current firmware version on affected devices and consult the Boyleep vendor advisory for patched firmware versions. Until patches can be applied, implement compensating controls: restrict physical access to devices through enclosures, locked cabinets, or controlled-access facilities; monitor device logs for unexpected administrative access; and consider isolating affected devices from sensitive networks if they store or process critical data.
Patch guidance
Check the Boyleep vendor advisory for patched firmware versions beyond 2.3.0.11291. Firmware updates should be staged in a test environment first to validate compatibility with your deployment. Plan updates during maintenance windows to minimize service disruption. Document the current firmware version before and after patching. If devices are managed centrally, prioritize bulk firmware deployment capabilities to update multiple units efficiently.
Detection guidance
Monitor for unauthorized access to factory test interfaces through device audit logs, if available. Look for unexpected administrative logins or configuration changes on affected devices. Inspect network traffic for unusual communication patterns from K11 y108 devices. Physical security monitoring—such as reviewing access logs to areas where these devices are located—may help identify unauthorized tampering. Correlate device logs with facility access records for suspicious activity.
Why prioritize this
While the CVSS score is MEDIUM (6.8), prioritization depends on your specific deployment context. If K11 y108 devices operate in physically controlled environments (data centers, locked facilities), the risk is lower and can be scheduled into normal patch cycles. If devices are deployed in public or semi-public spaces, remediation should be elevated to higher priority. The absence of KEV status suggests this is not an actively exploited vulnerability in the wild, but physical access exploits are inherently harder to detect, so assume-breach practices should apply.
Risk score, explained
The CVSS 3.1 score of 6.8 reflects a MEDIUM severity rating. Physical attack vector (AV:P) limits the threat to attackers with proximity, which reduces the base threat level compared to network-accessible exploits. However, the impact is complete: high confidentiality loss (C:H), high integrity loss (I:H), and high availability loss (A:H) once physical access is obtained. Low attack complexity (AC:L) and no privilege requirement (PR:N) mean exploitation is trivial once the attacker is physically present. The score appropriately balances limited access surface with severe consequences.
Frequently asked questions
Do we need to patch if our K11 y108 devices are in a locked server room?
The risk is significantly lower in physically secured environments, but patching remains best practice. Evaluate your facility access controls: who has key/badge access, how is physical access logged, and could an insider exploit this vulnerability? If access is tightly controlled and logged, you may prioritize this lower than devices in public spaces, but do not deprioritize indefinitely.
How do we check which firmware version is running on our devices?
Firmware version is typically available through the device web interface, SSH/CLI, or integrated management console. Consult your K11 y108 device documentation for the specific steps. Some organizations deploy SNMP or API queries to inventory device versions across multiple units. Document your current versions to establish a baseline before patching.
Will our network monitoring tools alert us if this vulnerability is exploited?
Detection is challenging because the attack requires physical access and direct manipulation of the device. Network-based detection may not catch local code execution on the device itself. Layer in physical security monitoring, device log review, and file integrity monitoring if available. A holistic approach—combining network, host, and physical controls—is most effective.
Is this vulnerability being actively exploited in the wild?
No, CVE-2026-36933 does not appear on CISA's Known Exploited Vulnerabilities (KEV) catalog as of the current date. This suggests no widespread public exploitation. However, the absence of a KEV listing does not mean exploits do not exist; physical access vulnerabilities are simply harder to weaponize and track at scale.
This analysis is based on publicly disclosed vulnerability information current as of the publication date. Patch availability, firmware version numbers, and vendor advisories should be verified directly with Boyleep. CVSS scores and severity ratings are provided as-is from the official vulnerability record. Organizations must conduct their own risk assessments based on their specific deployment, threat model, and control environment. Physical access vulnerabilities require context-specific evaluation; threat levels vary significantly between secure facilities and public deployments. This document does not constitute legal or compliance advice. Consult with your security team and vendor before making patching or mitigation decisions. Source: NVD (public-domain), retrieved 2026-07-23. Analysis generated by SEC.co (claude-haiku-4-5).
Weaknesses (CWE)
Related vulnerabilities
- CVE-2024-27891MEDIUMArista EOS MACsec + Egress ACL Policy Enforcement Failure
- CVE-2025-24165MEDIUMmacOS Permissions Issue Enables Unexpected System Termination
- CVE-2025-43339MEDIUMmacOS Tahoe Sandbox Access Control Bypass Allows User Data Disclosure
- CVE-2025-46308MEDIUMApple iOS, iPadOS, macOS Authorization Bypass—Sensitive Data Disclosure
- CVE-2026-10152MEDIUMImproper Access Control in TaleLin lin-cms-spring-boot Book Endpoint
- CVE-2026-10172MEDIUMBdtask Multi-Store Inventory 1.0 Unrestricted File Upload Vulnerability
- CVE-2026-10205MEDIUMUnrestricted File Upload in Metasoft MetaCRM 6.4.0 – Exploit Details & Remediation
- CVE-2026-10255MEDIUMPharmacy Sales System Authentication Bypass – SourceCodester 1.0