Device impersonation via non-unique MQTT credentials
Published Oct 12, 2025 · Updated Oct 18, 2025
Hard-coded credentials in Tomofun Furbo 360 and Furbo Mini firmware allow remote attackers to impersonate devices on the MQTT service. The nested furbo_img filesystem stores a non-unique MQTT client certificate and private key that extracted firmware exposes for reuse. Successful reuse reveals device identifiers and activity across deployed cameras; firmware retrieval and decryption make exploitation high-complexity.
Summary
What happened
Hard-coded credentials in Tomofun Furbo 360 and Furbo Mini firmware allow remote attackers to impersonate devices on the MQTT service. The nested furbo_img filesystem stores a non-unique MQTT client certificate and private key that extracted firmware exposes for reuse. Successful reuse reveals device identifiers and activity across deployed cameras; firmware retrieval and decryption make exploitation high-complexity.
The record
- CVE
- CVE-2025-11643
- Published
- Oct 12, 2025
- Updated
- Oct 18, 2025
- Vendor
- Tomofun
- Product
- Furbo Mini
- Classifications
- CWE-259, CWE-798, T1555.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 12, 2025CVE publishedPublication date reported by the CVE source.
- Oct 18, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=n/a
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- MQTT client-certificate replication stepsproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo