Raw vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2026-41446 is a critical-severity Use of Hard-coded Credentials (CWE-798) vulnerability in Snapone (inferred from references). Its CVSS base score is 9.2 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Unsecured Credentials (T1552); ranked at the 36th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to CM-2 (Baseline Configuration) and CM-7 (Least Functionality) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
Snap One WattBox 800 and 820 series devices running firmware versions prior to 2.10.0.0 are affected by CVE-2026-41446, a vulnerability involving undisclosed diagnostic HTTP endpoints. These endpoints use weak authentication that relies solely on the device's MAC address and service tag, both of which are printed in plaintext on the physical device label. This flaw, tied to CWE-798 (use of hard-coded credentials) and CWE-912 (hidden functionality), allows unauthorized access to sensitive diagnostic features.
Attackers who obtain the MAC address and service tag—through physical access to the device label, documentation, or other means—can remotely authenticate to the endpoints over the network with no privileges required. Successful exploitation enables execution of arbitrary commands as root on the device, potentially leading to full compromise, including high confidentiality, integrity, and availability impacts, as reflected in the CVSS v3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
The vendor's firmware release notes at https://help.snapone.com/wb-8x0-fw/Content/FW%20RN/8x0/8x0%20series%20FW%20RN.htm detail mitigation through upgrading to firmware version 2.10.0.0 or later, which addresses the exposed endpoints and authentication issues.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-26142
Vulnerability Data
Snap 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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Maintaining and reviewing a documented baseline configuration allows comparison that reveals any functionality absent from the approved specification.
Least-functionality configuration explicitly prohibits or restricts any capability not required by the approved baseline, blocking hidden additions.
Authenticator management requires secure distribution and handling of credentials, structurally discouraging hard-coded values.
Developer testing and evaluation activities are designed to discover undocumented or unspecified functionality after it has been introduced.
Cryptographic key management mandates proper establishment and handling instead of embedding keys in code.
Documented development processes and standards require all functionality to be specified and visible, structurally preventing undocumented hidden features.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prevent introduction of undocumented hidden functionality during development.
Pre-acquisition integrity/authenticity checks can detect undocumented hidden functions in supplied software/hardware.
PR.AA-01's credential/key-management processes can reduce the incentive to embed secrets but do not address or detect hard-coded values in source code, so the weakness remains fully possible.
PR.AA-02 addresses human identity proofing and per-person credential issuance at enrollment; it has no bearing on whether developers embed static credentials in software.
PR.DS-01 addresses encryption and integrity of stored data but never touches credential or key management practices, so it neither prevents hard-coded credentials nor removes any of their risk.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development and acceptance can discover undocumented functionality before release.
Change management processes can catch unauthorized additions but do not inherently prevent hidden functionality from being introduced.
Education on secure configuration practices discourages technical staff from embedding or relying on hard-coded credentials in systems and applications.
Monitoring activities can detect anomalous behavior from hidden functions but do not eliminate the weakness.
Secure key-generation, distribution and storage procedures reduce the likelihood that hard-coded or default cryptographic keys will be introduced or left unprotected.
Secure development life cycle mandates documented requirements and design reviews that would expose undocumented hidden functionality.