Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2025-11640 Overview
CVE-2025-11640 affects Tomofun Furbo 360 and Furbo Mini pet cameras. The vulnerability resides in the Bluetooth Low Energy (BLE) component and results in cleartext transmission of sensitive information [CWE-319, CWE-310]. An attacker with access to the local wireless range can intercept data exchanged between the device and a paired client. The firmware versions affected are Furbo 360 up to FB0035_FW_036 and Furbo Mini up to MC0020_FW_074. The vendor was contacted but did not respond. No patch has been released at the time of publication.
Critical Impact
Adjacent attackers within BLE range can observe sensitive information exchanged during device pairing or configuration due to the absence of transport encryption.
Affected Products
- Tomofun Furbo 360 Dog Camera firmware up to FB0035_FW_036
- Tomofun Furbo Mini firmware up to MC0020_FW_074
- Associated Furbo 360 and Furbo Mini hardware units running the above firmware
Discovery Timeline
- 2025-10-12 - CVE-2025-11640 published to NVD
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2025-11640
Vulnerability Analysis
The flaw stems from the Furbo camera's BLE provisioning channel transmitting sensitive data without encryption. During setup or reconfiguration, the device exchanges configuration parameters over BLE with a controlling mobile client. Because the exchange is sent in cleartext, an attacker within radio range can passively capture the traffic using standard BLE sniffing hardware. The exposed information falls under the confidentiality impact noted in the advisory, while integrity and availability are not affected. Exploitation requires adjacency to the device and precise timing during the BLE interaction, which the advisory classifies as high-complexity.
Root Cause
The root cause is the absence of a secure transport layer on the BLE interface. The firmware does not establish an encrypted BLE link or apply application-layer encryption before sending sensitive values. This maps to CWE-319 (Cleartext Transmission of Sensitive Information) and CWE-310 (Cryptographic Issues).
Attack Vector
An attacker must be within BLE range of the targeted camera, typically a few meters, and must capture traffic during an active provisioning or configuration event. Using a BLE sniffer, the attacker records the unencrypted advertisements and GATT exchanges, then extracts sensitive fields from the capture. The attack is passive and leaves no trace on the device. No code execution is achieved, and the vulnerability does not grant control of the camera.
No verified public proof-of-concept code is available. Refer to the VulDB Entry #328051 for the advisory record.
Detection Methods for CVE-2025-11640
Indicators of Compromise
- Unexpected BLE scanning or GATT connection attempts targeting Furbo devices during setup windows
- Presence of unauthorized BLE sniffing hardware (for example, nRF52-based dongles) in proximity to deployed cameras
- Repeated factory resets or re-provisioning events on a Furbo device without administrator action
Detection Strategies
- Monitor wireless spectrum logs from managed access points for anomalous BLE activity near pet-camera deployments
- Correlate mobile application pairing events with device-side provisioning timestamps to identify out-of-band sessions
- Audit the Furbo cloud account for logins or configuration changes that do not match owner activity
Monitoring Recommendations
- Enable account-level alerts in the Furbo mobile application for new device enrollments and setting changes
- Deploy wireless intrusion detection where IoT devices handle configuration data
- Review network telemetry for new outbound connections from the camera following any suspected BLE event
How to Mitigate CVE-2025-11640
Immediate Actions Required
- Perform BLE provisioning only in a physically controlled area with no untrusted parties within radio range
- Avoid repeated re-pairing of the camera, which maximizes exposure windows for BLE interception
- Place Furbo cameras on an isolated IoT network segment that restricts lateral access to primary user devices
- Rotate any Wi-Fi credentials or account passwords that may have been transmitted during past provisioning events
Patch Information
No vendor patch is available. The advisory states that Tomofun did not respond to the disclosure. Users should monitor the VulDB CTI Report #328051 for updates and check the Furbo application for any future firmware releases beyond FB0035_FW_036 and MC0020_FW_074.
Workarounds
- Disable or power down the camera when BLE provisioning is not actively required
- Segment the camera on a dedicated VLAN or guest Wi-Fi network to limit exposure of adjacent credentials
- Replace affected devices with alternatives that support authenticated and encrypted BLE pairing where cleartext exposure is unacceptable
# Example: isolate Furbo cameras on a restricted VLAN at the gateway
# (adjust interface and subnet to your environment)
iptables -I FORWARD -i vlan-iot -o vlan-lan -j DROP
iptables -I FORWARD -i vlan-lan -o vlan-iot -m state --state ESTABLISHED,RELATED -j ACCEPT
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

