CVE-2025-11638
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA flaw has been found in Tomofun Furbo 360 and Furbo Mini. The affected element is an unknown function of the component Bluetooth Handler. Executing manipulation can lead to denial of service. The attacker needs to be present on the local network. 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA denial of service vulnerability exists in the Bluetooth Handler component of Tomofun Furbo 360 and Furbo Mini pet cameras. An attacker present on the local network can manipulate Bluetooth communications to cause the device to become unavailable or unresponsive. Affected versions are Furbo 360 up to FB0035_FW_036 and Furbo Mini up to MC0020_FW_074.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 074<= 036CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the Furbo device modelLocate the model number on the device packaging, physical device label, or in the mobile app device settings. Confirm it is either Furbo 360 or Furbo Mini.Affected if The device is a Furbo 360 or Furbo Mini pet camera.
-
Determine the installed firmware versionAccess the Furbo mobile app, navigate to device settings, and locate the firmware version information. Alternatively, check via the device web interface if available.Affected if Firmware version is FB0035_FW_036 or lower for Furbo 360, or MC0020_FW_074 or lower for Furbo Mini.
-
Verify Bluetooth is enabled on the deviceCheck the device settings in the Furbo mobile app or on the physical device status indicators to confirm Bluetooth functionality is active.Affected if Bluetooth is enabled, as the vulnerability exists in the Bluetooth Handler component.
-
Assess network accessibilityDetermine if the device is connected to a local network that allows access from other devices on that network. Check router or network device listings for the Furbo device IP address and confirm it is reachable.Affected if The device is on a shared local network where untrusted devices or users could potentially access it.
You are affected if you own a Furbo 360 (firmware FB0035_FW_036 or below) or Furbo Mini (firmware MC0020_FW_074 or below) with Bluetooth enabled, and the device is accessible from your local network.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataSince the vendor did not respond to disclosure and no patch is available, network segmentation isolating IoT devices from the main network, along with strict access control policies to limit local network access to authorized users, are recommended compensating controls.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11638 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-11638 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data