Furbo 360 and Furbo Mini
CVE-2025-11647
LOW
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDiscover Furbo device via BLE scan
-
DeliveryEnumerate GATT services
-
ExploitCraft DeviceToken manipulation request
-
ExecutionSend malicious GATT message
-
PersistExtract token from response
-
ImpactPotential unauthorized cloud access
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the attacker to be on the same local network (adjacent network) as the target Furbo camera. The device must have Bluetooth enabled and discoverable (default configuration for functionality). The attacker must possess detailed knowledge of the BLE GATT service structure and crafting techniques to manipulate the DeviceToken argument-this is not trivial reconnaissance and explains the high attack complexity (AC:H) rating. No authentication is required from the camera's perspective (PR:N), as BLE discovery and GATT service enumeration are typically unauthenticated on consumer IoT devices. The attack does not require user interaction (UI:N). Limiting factors include: (1) requirement for local/adjacent network access, eliminating remote exploitation; (2) high attack complexity necessitating specialized BLE exploitation skills; (3) no widespread tooling or low-skill exploits publicly available despite POC existence; (4) limited impact scope (confidentiality only, no integrity or availability impact). |
| Impact | This vulnerability presents a low real-world risk despite its straightforward nature. The CVSS 4.0 score of 1.3 reflects the significant barriers to exploitation: adjacent attack vector (AV:A, not network), high attack complexity (AC:H), and low confidentiality impact (VC:L). The EPSS score of 0.03% (9th percentile) indicates minimal exploitation probability in the wild, suggesting this is not a widespread concern despite POC availability. The attack requires specific conditions-local network proximity, high technical skill, and detailed knowledge of BLE GATT internals. However, the vendor's lack of response (no patched firmware versions available) means affected devices remain permanently vulnerable. Risk is contextual: homes with Furbo cameras on isolated IoT networks face minimal threat; however, corporate or shared network environments where an attacker can achieve local network access would have elevated risk. The divergence between POC availability (publicly available) and EPSS exploitation probability (0.03%) suggests the POC is technically competent but requires sufficient expertise to weaponize that most attackers lack. |
| Exploit ScenarioDerived | An attacker on the same local network as a Furbo 360 or Mini camera (e.g., a guest on the home WiFi or compromised IoT device on the network) discovers the target camera via BLE scanning. The attacker uses publicly available exploit code from the GitHub advisory to craft a malicious GATT Service request that manipulates the DeviceToken argument, causing the camera to leak the token. The attacker extracts the DeviceToken, potentially enabling unauthorized access to the device's cloud services or remote control features depending on how the token is used by the Furbo mobile application. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 29, 2026
Information disclosure vulnerability in Tomofun Furbo 360 and Furbo Mini dog cameras allows local network attackers to extract sensitive DeviceToken data via manipulation of GATT Service arguments. The attack requires high technical complexity and adjacency to the target network. Publicly available exploit code exists; however, the extremely low EPSS score (0.03%) and requirement for local network access and high attack complexity suggest limited real-world exploitation likelihood despite POC availability.
RemediationAI
No vendor-released patch exists for this vulnerability. Primary mitigation requires network-level controls: restrict BLE device discovery and connection attempts to authorized devices only, implement network segmentation to isolate Furbo cameras on a dedicated IoT VLAN or separate wireless network with restricted inbound access, and disable Bluetooth connectivity if not actively required for the camera's intended functionality. If Bluetooth must remain enabled, restrict the SSID broadcast and use strong WiFi encryption (WPA3 preferred) to limit local network access. Alternatively, consider replacing affected Furbo models with pet cameras from vendors with active security maintenance and patch deployment histories. Monitor local network traffic for unauthorized BLE connections or DeviceToken exfiltration patterns. Users should review Tomofun's security advisories at https://vuldb.com/?ctiid.328058 for any future firmware updates, though the vendor's historical non-responsiveness suggests updates are unlikely.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability resides in the Bluetooth Low Energy (BLE) GATT (Generic Attribute Profile) service implementation of Furbo smart pet cameras. GATT is a protocol for discovering services and characteristics over BLE connections. The flaw in the unknown processing component of the GATT Service allows attackers on the local network to manipulate the DeviceToken argument to trigger information disclosure. CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) indicates that authentication mechanisms or access controls are insufficient to prevent token extraction. The affected firmware versions are Furbo 360 up to FB0035_FW_036 and Furbo Mini up to MC0020_FW_074, with no patched versions released by the vendor.
Know when Furbo Mini Firmware 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:A/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P
Primary rating from Vendor (vuldb) · only source for this CVE.
CVSS VectorVendor: vuldb
DescriptionCVE.org
A flaw has been found in Tomofun Furbo 360 and Furbo Mini. This issue affects some unknown processing of the component GATT Service. This manipulation of the argument DeviceToken causes information disclosure. The attack is only possible within the local network. A high degree of complexity is needed for the attack. The exploitability is assessed as difficult. The firmware versions determined to be affected are Furbo 360 up to FB0035_FW_036 and Furbo Mini up to MC0020_FW_074. The vendor was contacted early about this disclosure but did not respond in any way.
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.
Affected Products (CPE)CVE.org
More in Furbo Mini Firmware
View allInsecure local storage in Tomofun Furbo 360 and Furbo Mini firmware lets authenticated local users with low privileges a
Server-side request forgery in Tomofun Furbo 360 and Furbo Mini dog cameras allows remote attackers to manipulate the TF
A hard-coded root password in the Tomofun Furbo 360 and Furbo Mini pet cameras allows local attackers with low privilege
Hard-coded MQTT client certificate credentials in Furbo 360 (up to FB0035_FW_036) and Furbo Mini (up to MC0020_FW_074) f
Tomofun Furbo 360 and Furbo Mini dog cameras running firmware up to FB0035_FW_036 and MC0020_FW_074 do not properly vali
Improper access controls in the GATT Service of Tomofun Furbo 360 and Furbo Mini dog cameras allow local network attacke
Denial of service in Tomofun Furbo 360 and Furbo Mini cameras allows unauthenticated attackers on the adjacent network (
Insecure storage of sensitive information in Tomofun Furbo 360 and Furbo Mini dog cameras via UART interface allows phys
Weak cryptographic hash implementation in Tomofun Furbo 360 and Furbo Mini firmware allows local attackers with low priv
Denial of service in Tomofun Furbo 360 and Furbo Mini pet cameras occurs through the Registration Handler when a physica
Physical access to the UART debug interface on Tomofun Furbo 360 (firmware up to FB0035_FW_036) and Furbo Mini (up to MC
Cleartext transmission of sensitive information over Bluetooth Low Energy in Tomofun Furbo 360 and Furbo Mini firmware (
NVD
CVE.org
EPSS
GitHub
VulDB
Exploit-DB