Skip to main content
Vulnerability Database/CVE-2025-11638

CVE-2025-11638: Furbo Mini Firmware DOS Vulnerability

CVE-2025-11638 is a denial of service flaw in Furbo Mini and Furbo 360 firmware that allows local network attackers to disrupt device operations. This post explains its impact, affected versions, and mitigation steps.

Published:

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-11638 Overview

CVE-2025-11638 is a denial of service vulnerability affecting Tomofun Furbo 360 and Furbo Mini pet cameras. The flaw resides in an unknown function of the Bluetooth Handler component. An attacker on the adjacent network can manipulate Bluetooth traffic to disrupt device availability. The weakness is classified under [CWE-404] Improper Resource Shutdown or Release.

Affected firmware versions include Furbo 360 up to FB0035_FW_036 and Furbo Mini up to MC0020_FW_074. The vendor was contacted prior to disclosure but did not respond. No patch is currently available.

Critical Impact

Attackers within Bluetooth range can trigger a denial of service condition on affected Furbo cameras, disrupting pet monitoring functionality.

Affected Products

  • Tomofun Furbo 360 Dog Camera firmware up to FB0035_FW_036
  • Tomofun Furbo Mini firmware up to MC0020_FW_074
  • Furbo 360 and Furbo Mini hardware devices running affected firmware

Discovery Timeline

  • 2025-10-12 - CVE-2025-11638 published to NVD
  • 2026-10-18 - Last updated in NVD database

Technical Details for CVE-2025-11638

Vulnerability Analysis

The vulnerability exists in the Bluetooth Handler component of Furbo 360 and Furbo Mini cameras. An unidentified function within the handler fails to properly manage resources when processing crafted Bluetooth input. This improper resource shutdown or release ([CWE-404]) leads to a denial of service condition on the affected device.

Exploitation requires the attacker to be present on the local network or within Bluetooth range of the camera. No authentication or user interaction is required to trigger the condition. The impact is limited to availability of the device — confidentiality and integrity are not affected.

Root Cause

The root cause is improper resource shutdown or release in the Bluetooth Handler. When specific manipulated input is received, the handler does not correctly deallocate or terminate resources. This leaves the service in an unusable state and prevents normal operation of the camera.

Attack Vector

The attack vector is adjacent network access. An attacker within Bluetooth range transmits malformed or unexpected data to the camera's Bluetooth Handler. Processing the input triggers the resource handling flaw and causes the service to become unavailable. See the VulDB entry #328049 for additional technical context.

// No verified public exploit code is available for CVE-2025-11638.
// The vulnerability is triggered by sending crafted Bluetooth input
// to the affected handler on devices within adjacent network range.

Detection Methods for CVE-2025-11638

Indicators of Compromise

  • Unexpected reboots, crashes, or unresponsive states on Furbo 360 or Furbo Mini devices
  • Loss of camera livestream or app connectivity coinciding with proximity of unknown Bluetooth devices
  • Repeated reconnection attempts between the mobile app and the affected device

Detection Strategies

  • Monitor wireless and Bluetooth activity near deployed Furbo devices for unauthorized scanning or pairing attempts
  • Track device availability metrics from the Furbo mobile application and correlate outages with network events
  • Review home or small-business network logs for unknown devices appearing on segments that host IoT cameras

Monitoring Recommendations

  • Enable network-level IoT monitoring to flag anomalous Bluetooth or wireless traffic directed at camera devices
  • Alert on repeated device offline events that cannot be attributed to power or Wi-Fi loss
  • Audit the Bluetooth attack surface periodically using wireless assessment tools

How to Mitigate CVE-2025-11638

Immediate Actions Required

  • Restrict physical proximity and wireless access to Furbo 360 and Furbo Mini devices wherever possible
  • Disable Bluetooth on affected cameras after initial setup if the feature is not required for ongoing operation
  • Place IoT cameras on an isolated network segment separate from sensitive assets

Patch Information

No vendor patch is available at the time of publication. The vendor was contacted prior to disclosure but did not respond. Monitor the VulDB advisory and official Furbo channels for firmware updates addressing CVE-2025-11638.

Workarounds

  • Deploy affected cameras in physical locations where adjacent attackers cannot reach Bluetooth range
  • Segment IoT devices on a dedicated VLAN or guest network to limit lateral exposure
  • Power cycle affected devices to restore service if a denial of service condition occurs
  • Consider replacement with an alternative device if availability of the camera is business-critical
bash
# Example: isolate IoT cameras on a dedicated VLAN (vendor-neutral)
# Replace interface and VLAN IDs to match your environment
ip link add link eth0 name eth0.50 type vlan id 50
ip addr add 192.168.50.1/24 dev eth0.50
ip link set dev eth0.50 up
# Apply firewall rules preventing IoT VLAN from reaching trusted subnets
iptables -A FORWARD -i eth0.50 -o eth0.10 -j DROP

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

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.