CVE-2026-41446
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 · uneditedSnap One WattBox 800 and 820 series firmware versions prior to 2.10.0.0 contain undisclosed diagnostic HTTP endpoints that require only the device MAC address and service tag for authentication, both of which are printed in plaintext on the physical device label. Attackers with access to the device label or documentation containing these values can authenticate to the several endpoints and execute arbitrary commands as root on the device.
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 · high confidenceThe WattBox 800 and 820 series devices contain undocumented HTTP diagnostic endpoints in firmware versions prior to 2.10.0.0 that use a weak authentication mechanism requiring only the device MAC address and service tag—both printed on the physical device label. An attacker with access to these values (from the physical label or accompanying documentation) can authenticate to these endpoints and execute arbitrary commands with root privileges.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 WattBox device modelLocate the physical device or access its management interface and confirm it is a WattBox 800 or 820 series unit by checking the model number in the web UI or on the device chassis label.Affected if The device is a WattBox 800 or 820 series model.
-
Check the installed firmware versionAccess the device's web management interface, typically at its IP address, and navigate to the System or Status page to view the firmware version. Alternatively, check the label on the device for a firmware version printed there.Affected if The firmware version is below 2.10.0.0.
-
Locate the MAC address and service tag from the device labelPhysically inspect the device label on the chassis or locate these values in the device documentation or management interface. Note both the MAC address (typically in format XX:XX:XX:XX:XX:XX) and the service tag (alphanumeric string).Affected if The MAC address and service tag are visible, printed, or accessible from documentation.
-
Test for hidden diagnostic HTTP endpointsUsing a web browser or HTTP client, attempt to access common diagnostic paths such as /diag, /diagnostics, /debug, or /cgi-bin/diag on the device's IP address. Look for endpoints that prompt for authentication or return diagnostic pages.Affected if Hidden diagnostic HTTP endpoints are present and accessible without full credentials.
-
Verify MAC address and service tag authenticationIf diagnostic endpoints are found, attempt to authenticate using only the MAC address and service tag values as credentials. Observe whether authentication succeeds with these values alone.Affected if Authentication succeeds using only the MAC address and service tag without requiring a password.
A user is affected if they have a WattBox 800 or 820 series device running firmware below version 2.10.0.0 where hidden diagnostic endpoints accept MAC address and service tag as sole authentication credentials.
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.
dbcve · scopedUpdate all affected WattBox devices to firmware version 2.10.0.0 or later, and implement physical access controls to prevent unauthorized access to device labels and documentation containing MAC addresses and service tags.
Firmware version 2.10.0.0 or later for WattBox 800 and 820 series
- Identify the specific WattBox model (800 or 820 series) and current firmware version via the device web interface or physical label
- Download the latest firmware version 2.10.0.0 or later from Snap One's official support site (help.snapone.com)
- Access the device administration panel and navigate to the firmware update section
- Upload and apply firmware version 2.10.0.0
- Verify the upgrade was successful by checking the firmware version displayed in the web interface
- After upgrade, confirm the diagnostic HTTP endpoints are no longer accessible without proper authentication
- If available, change the default service tag through the administration interface to further reduce attack surface
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41446 — 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-41446 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