dbcve.org
Furbo Mini FirmwareOperating system · Furbo

CVE-2025-11643

HIGH · 8.1 CVSS v3.1 Published 2025-10-12
Fix available
A fix is available. Upgrade to after 074 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
A security flaw has been discovered in Tomofun Furbo 360 and Furbo Mini. Affected by this vulnerability is an unknown functionality of the file /squashfs-root/furbo_img of the component MQTT Client Certificate. Performing manipulation results in hard-coded credentials. The attack may be initiated remotely. The attack's complexity is rated as high. The exploitation appears to be 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.

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 · high confidence

Hard-coded credentials are embedded in the MQTT Client Certificate functionality within the /squashfs-root/furbo_img file on Tomofun Furbo 360 and Furbo Mini pet cameras. These credentials can be extracted by an attacker who has network access to the device, potentially allowing unauthorized access to the MQTT broker and the device's communication channels.

MitigationSince the vendor did not respond to the disclosure, pursue network segmentation to isolate IoT devices, implement firewall rules restricting MQTT traffic, and contact Tomofun support requesting firmware updates that remove hard-coded credentials. Until a patch is available, monitor for unauthorized MQTT connections.

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
Furbo Mini FirmwareOperating system
Affected:<= 074
Furbo 360 Dog Camera FirmwareOperating system
Affected:<= 036

CVSS 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
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Determine if the device is a Tomofun Furbo Mini or Furbo 360 pet camera. Check device labeling, management interface, or API endpoint responses for model identification.
    Affected if Device is NOT a Furbo Mini or Furbo 360 camera (not affected).
  2. Check firmware version for Furbo Mini
    Access the device's admin interface or check via API to retrieve the firmware version. Compare the version number to the vulnerable threshold.
    Affected if Device is a Furbo Mini with firmware version 074 or lower (affected).
  3. Check firmware version for Furbo 360
    Access the device's admin interface or check via API to retrieve the firmware version. Compare the version number to the vulnerable threshold.
    Affected if Device is a Furbo 360 with firmware version 036 or lower (affected).
  4. Verify vulnerable file presence
    If firmware extraction is possible, examine the firmware image for the presence of the file /squashfs-root/furbo_img which contains the hard-coded MQTT credentials.
    Affected if The file /squashfs-root/furbo_img exists in the firmware and contains embedded credentials (affected).
  5. Check MQTT client configuration
    Inspect the device configuration or captured network traffic for MQTT connections. Determine if the device is configured to use client certificate authentication.
    Affected if MQTT client certificate functionality is enabled and the device connects to an MQTT broker (potentially affected if firmware version is vulnerable).

The device is affected if it is a Furbo Mini (firmware <=074) or Furbo 360 (firmware <=036) with hard-coded credentials embedded in the /squashfs-root/furbo_img file used for MQTT client certificate authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 074
Interim mitigation

Since the vendor did not respond to the disclosure, pursue network segmentation to isolate IoT devices, implement firewall rules restricting MQTT traffic, and contact Tomofun support requesting firmware updates that remove hard-coded credentials. Until a patch is available, monitor for unauthorized MQTT connections.

Fix this in Furbo Mini Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11643 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-11643 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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