CVE-2026-4149
Memory Safety in Sonos Era 300 Firmware ≤ 83.1-61240
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2026-4149 is a critical-severity Improper Restriction of Operations within the Bounds of a Memory Buffer (CWE-119) vulnerability in Sonos Era 300 Firmware. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Process Injection (T1055); ranked in the top 40% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-8 (Security and Privacy Engineering Principles) and SI-10 (Information Input Validation) — 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.
This vulnerability is an out-of-bounds memory access flaw in the Sonos Era 300 smart speaker that leads to remote code execution. It resides in the handling of the DataOffset field inside inbound SMB responses, where insufficient validation of attacker-supplied values permits access beyond the end of an allocated buffer. The resulting memory corruption occurs in kernel context and carries a CVSS 3.1 score of 9.8.
Remote, unauthenticated attackers can send a crafted SMB response to an affected device and achieve arbitrary code execution without user interaction. The attack requires only network adjacency to the target and exploits the device’s SMB client implementation directly.
The issue was reported as ZDI-CAN-28345 and is covered by Zero Day Initiative advisory ZDI-26-192. No additional mitigation details are supplied in the available reference.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-21627
Vulnerability Data
Sonos Era 300 SMB Response Out-Of-Bounds Access Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Sonos Era 300. Authentication is not required to exploit this vulnerability. The specific flaw exists within…
more
the handling of the DataOffset field within SMB responses. The issue results from the lack of proper validation of user-supplied data, which can result in a memory access past the end of an allocated buffer. An attacker can leverage this vulnerability to execute code in the context of the kernel. Was ZDI-CAN-28345.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V17.3.2
Mitigating Controls (NIST 800-53 r5) AI
Secure engineering principles require memory-safe design and coding that structurally avoids buffer-boundary violations.
Input validation directly enforces bounds checking that stops out-of-bounds reads/writes from being introduced or reached.
Memory protection restricts exploitation impact of buffer overflows without eliminating the underlying coding flaw.
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 (bounds checking, safe APIs, reviews) directly prevent this class of flaw.
Vulnerability scanning and code analysis directly surface buffer-boundary flaws.
Receiving and triaging vulnerability disclosures commonly includes buffer-related reports.
Developer training on secure coding reduces introduction of memory-buffer errors.
Patching replaces vulnerable code containing buffer-boundary defects.
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 catches out-of-bounds accesses before release, covering most instances of the weakness.
Secure development lifecycle mandates memory-safety practices that directly prevent buffer-boundary violations.
Application security requirements can specify memory-safety rules, but do not prescribe implementation details.
Secure architecture and engineering principles include memory-safe design patterns that mitigate buffer overflows.
Secure coding standards explicitly forbid unsafe buffer operations, directly eliminating CWE-119.