CVE-2026-0842
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 Flycatcher Toys smART Sketcher up to 2.0. This affects an unknown part of the component Bluetooth Low Energy Interface. This manipulation causes missing authentication. The attack can only be done within the local network. The exploit has been published and may be used. 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 smART Sketcher toy device has a missing authentication vulnerability in its Bluetooth Low Energy (BLE) interface, allowing unauthenticated attackers within the local network to interact with the device. The attack is limited to local network proximity, but a working exploit has been publicly disclosed.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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 smART Sketcher devicePhysically inspect your environment for the smART Sketcher toy, or use a Bluetooth scanner to look for devices advertising a name containing 'smART Sketcher' or similar toy-related BLE device names in your vicinityAffected if A smART Sketcher device is present and advertising via BLE
-
Confirm BLE is enabled on the deviceVerify the device is powered on and in active/paired mode. Use a BLE scanner app or tool (such as hcitool, gatttool, or a mobile BLE scanner app) to detect if the device is advertisingAffected if The device is powered on and actively advertising BLE signals, making it discoverable
-
Test BLE connection without authenticationUsing a BLE client tool (like gatttool, bleah, or a mobile app such as nRF Connect), attempt to connect to the device and access its services or characteristics without providing any PIN, passkey, or pairing credentialsAffected if A connection can be established and device services/characteristics are readable or writable without any authentication challenge
-
Check device network proximityDetermine if the device is within BLE radio range (typically 10-100 meters indoors) from untrusted actors. Note the physical location of the device and assess whether unauthorized individuals could approach that rangeAffected if The device is in an accessible area where unknown users could be within BLE range
If you have a smART Sketcher device that is powered on with BLE enabled and accepts connections without any authentication, your environment is affected by this vulnerability.
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, apply network segmentation to isolate IoT/toy devices on a separate VLAN, disable BLE when not in use, and monitor for unauthorized BLE device interactions. Consider retiring or replacing the device if a firmware update is not forthcoming.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0842 — 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-2026-0842 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