Onyx Cookware Nexsmart Guardian 2 alert suppression via deauthentication in phone alerts
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
The Nexsmart Guardian 2 (Alarm system) from Onyx Cookware ApS can stop sending phone alerts for events such as arming, disarming, and tamper events. An attacker on an adjacent network can do this without logging in or any user action by forcing the device off its Wi-Fi network with a deauthentication attack, and alerts missed during that time are never sent after the connection returns.
Written by a model
Original description
The device only supports Wi-Fi protocols vulnerable to deauthentication attacks (WEP/WPA/WPA2). Should any event which would typically be logged to the user’s mobile device (such as arming or disarming the alarm or any tamper events) be incurred whilst the device is temporarily disconnected from its Wi-Fi network (such as via a deauthentication attack), those alerts will not be sent even after connection is regained.
What to do
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-82950 (Alert suppression through deauthentication-induced notification failure), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-82950 (entry last updated 2026-11-19):
Affected:
- Onyx Cookware ApS Nexsmart Guardian 2 (Alarm system): versions 0
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-82950 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-82950 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://medium.com/@enalindstrom/learning-iot-security-with-the-nexsmart-guardian-2-8028d55c430c
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-82950
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-82950"}.Affected versions
- Onyx Cookware ApS Nexsmart Guardian 2 (Alarm system)0
cve.now Index
- Exploitation0/40No signal
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch5/5No patch listed yet
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 34 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-82950 |
| Record | NVD · CVE-2026-82950 |
| Other links 1 | |
| Link | medium.com · @enalindstrom/learning-iot-security-with-the-nexsmart-guardian-2-8028d55c430c |
Questions about CVE-2026-82950
Is CVE-2026-82950 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-82950?
Nexsmart Guardian 2 (Alarm system): version 0.
Source: cve.now feed data
Related
- CVE-2026-82949Occupancy monitoring via unencrypted RF communication
- CVE-2026-82948RF Replay of control commands
- CVE-2026-122192Guest access to Firecracker process memory after a failed memory discard
- CVE-2026-102280Sandboxie-Plus: Sandbox containment bypass
- CVE-2026-62275Detection of error condition without action in the MigTD's vmcall_raw transport for the Intel(R) TDX Migration Trust Domain (MigTD) within…
- CVE-2026-68541PolicyPress: Sensitive content disclosed via CSS-only web redaction and insecure starter workflow defaults
No corrections so far. Something wrong on this page? Report an error.