CVE-2025-11633
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 vulnerability was identified in Tomofun Furbo 360 and Furbo Mini. Affected by this issue is the function upload_file_to_s3 of the file collect_logs.sh of the component HTTP Traffic Handler. The manipulation leads to improper certificate validation. The attack may be initiated remotely. The attack is considered to have high complexity. The exploitation is known 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 · moderate confidenceThe Furbo 360 and Furbo Mini pet cameras contain an improper certificate validation vulnerability in the upload_file_to_s3 function within the collect_logs.sh script (HTTP Traffic Handler). This allows man-in-the-middle attackers to intercept or tamper with S3 log uploads by presenting invalid certificates. The high attack complexity and difficulty of exploitation align with the CVSS 5.9 rating.
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
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
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 Furbo device modelLocate the model number on the device or check the mobile app/device documentation to confirm whether it is a Furbo Mini or Furbo 360 Dog Camera.Affected if The device is a Furbo Mini or Furbo 360 model.
-
Determine firmware versionAccess the Furbo mobile app settings, check the device web interface if available, or consult vendor documentation for firmware version retrieval instructions. Look for a version number in the format like '074' for Furbo Mini or '036' for Furbo 360.Affected if The firmware version is 074 or lower for Furbo Mini, or 036 or lower for Furbo 360.
-
Locate collect_logs.sh scriptIf you have shell access or can extract the firmware image, locate the collect_logs.sh script - typically found in the device filesystem under /usr/bin, /bin, or a similar scripts directory.Affected if The collect_logs.sh script exists on the device firmware.
-
Inspect upload_file_to_s3 functionOpen the collect_logs.sh script and examine the upload_file_to_s3 function. Look for curl or wget commands that upload to S3 and check whether the --cacert, -k, --insecure, or similar options are used to bypass certificate validation.Affected if The upload_file_to_s3 function uses options that disable certificate validation (such as -k or --insecure) or lacks proper certificate verification flags.
-
Verify cloud logging feature is enabledCheck the Furbo mobile app settings or device configuration to determine if cloud logging or remote log upload functionality is enabled.Affected if Cloud logging to S3 is enabled on the device.
A user is affected if they own a Furbo Mini on firmware <=074 or Furbo 360 on firmware <=036, with cloud logging enabled, and the collect_logs.sh script lacks proper certificate validation in its S3 upload function.
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, implement network segmentation to isolate Furbo devices and consider disabling the cloud logging feature if possible. Monitor for unauthorized network behavior and evaluate device replacement if the vendor does not release a patch.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11633 — 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-11633 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