dbcve.org
Era 300 FirmwareOperating system · Sonos

CVE-2025-1051

HIGH · 8.8 CVSS v3.0 Published 2025-06-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
No privileges Zero-click

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 · unedited
Sonos Era 300 Heap-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected Sonos Era 300 speakers. Authentication is not required to exploit this vulnerability. The specific flaw exists within the processing of ALAC data. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a heap-based buffer. An attacker can leverage this vulnerability to execute code in the context of the anacapa user. Was ZDI-CAN-25865.

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 confidence

A heap-based buffer overflow vulnerability exists in Sonos Era 300 speakers during ALAC (Apple Lossless Audio Codec) audio data processing. The flaw stems from insufficient validation of user-supplied data length before copying into heap-allocated memory, allowing network-adjacent unauthenticated attackers to overflow the heap buffer and execute arbitrary code as the unprivileged 'anacapa' user.

MitigationIsolate Sonos Era 300 devices on a restricted network segment to limit exposure to adjacent attackers until the vendor releases an official firmware patch, then apply the update promptly.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Era 300 FirmwareOperating system
Affected:= 81.1-58074

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:A/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the Sonos app or web interface and verify the device is a Sonos Era 300 speaker. This can also be confirmed via the Sonos S2 controller by navigating to Settings > System > About My System.
    Affected if The device model is Sonos Era 300.
  2. Check the installed firmware version
    In the Sonos app, go to Settings > System > System Info > Software to view the current firmware version. Alternatively, access the device via SSH if enabled and run: cat /etc/os-release or check /version.txt.
    Affected if The firmware version is 81.1-58074.
  3. Confirm ALAC audio processing capability
    ALAC (Apple Lossless Audio Codec) decoding is a built-in capability of the Sonos Era 300. The vulnerability triggers when the device processes ALAC-encoded audio streams. This feature is active whenever the device plays ALAC content from Apple devices or files.
    Affected if The device is capable of playing ALAC-encoded audio, which is enabled by default on the Era 300.
  4. Verify network exposure
    Check whether the Sonos Era 300 is accessible on an untrusted network segment. Review network configuration to determine if the device is on a shared or guest network where adjacent attackers could reach it.
    Affected if The device is reachable by network-adjacent attackers without network segmentation.

A user is affected if they have a Sonos Era 300 speaker running firmware version 81.1-58074 that is accessible on a network where adjacent attackers can send specially crafted ALAC audio data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Isolate Sonos Era 300 devices on a restricted network segment to limit exposure to adjacent attackers until the vendor releases an official firmware patch, then apply the update promptly.

Fix this in Era 300 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1051 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-1051 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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