Skip to main content
Menu
CVEs

Onyx Cookware Nexsmart Guardian 2 cleartext 433 MHz radio leaks occupancy monitoring

CVE-2026-82949EUVD-2026-129655GHSA-QJ6H-WCWM-2FW4Published November 19, 2026, updated

7.1HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Summary

Onyx Cookware ApS's Nexsmart Guardian 2 (Alarm system) sends sensor messages over 433.92 MHz radio using static, unencrypted codes. An attacker within radio range, without logging in or any action by the user, can use this traffic to monitor people's movements inside the premises where the sensors are installed.

Written by a model

Original description

The static codes used for information transmission throughout the 433.92 MHz system of the Guardian 2 system allow an attacker in proximity to monitor the movements of users inside the premises where the sensors are set up. This is further aided by the fact that codes transmitted reveal sensor type, although sensor location cannot be inferred from this traffic alone.

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-82949 (Occupancy monitoring via unencrypted RF communication), 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-82949 (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-82949 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-82949 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-82949
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-82949"}.

Affected versions

cve.now Index

12Pof 100 · provisional · methodology v3
  • 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

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 3

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-82949
RecordNVD · CVE-2026-82949
Other links 1
Linkmedium.com · @enalindstrom/learning-iot-security-with-the-nexsmart-guardian-2-8028d55c430c

Questions about CVE-2026-82949

Is CVE-2026-82949 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-82949?

Nexsmart Guardian 2 (Alarm system): version 0.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.