dbcve.org
S2Application · Sonos

CVE-2025-1050

HIGH · 8.8 CVSS v3.0 Published 2025-04-23
Fix available
A fix is available. Upgrade to 83.1-61240 or later.
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 Out-of-Bounds Write 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 HLS playlist data. The issue results from the lack of proper validation of user-supplied data, which can result in a write past the end of an allocated data structure. An attacker can leverage this vulnerability to execute code in the context of the anacapa user. Was ZDI-CAN-25606.

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 · moderate confidence

The vulnerability is an out-of-bounds write flaw in the HLS playlist parser of Sonos Era 300 speakers. By sending specially crafted HLS playlist data without authentication, a network-adjacent attacker can write beyond allocated buffer boundaries and achieve code execution in the context of the unprivileged 'anacapa' user.

MitigationSince Sonos must release a firmware patch to address the root cause, immediate compensating controls should include network segmentation to restrict physical or logical access to the speaker's management interfaces, and monitoring for anomalous HLS traffic patterns until an official patch is available.

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
S2Application
Affected:< 83.1-61240

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
    Locate the physical label on the Sonos speaker or check the device details in the Sonos app under System > About My System. Confirm the model is Era 300.
    Affected if The device is not a Sonos Era 300 speaker, then this specific CVE does not apply.
  2. Check the firmware version
    In the Sonos app, go to System > About My System and note the version number listed for the Era 300 speaker. Compare it against the affected version range: Sonos S2 versions prior to 83.1-61240.
    Affected if The installed firmware version is lower than 83.1-61240, the device falls within the affected version range.
  3. Verify HLS streaming is in use
    Review any configured audio streaming sources or automation rules on the speaker. HLS (HTTP Live Streaming) is commonly used for internet radio or cloud-based audio services. Check if the speaker is configured to receive HLS streams from any source.
    Affected if The HLS playlist parser is only vulnerable when the speaker is actively processing HLS playlist data; if HLS streaming is not configured or used, the attack surface may not be present.
  4. Assess network accessibility
    Determine if the speaker's management interfaces are accessible from untrusted network segments. This can include checking firewall rules, VLAN configuration, or whether the speaker is on a guest or isolated network.
    Affected if The vulnerability is exploitable by a network-adjacent attacker; if the device is not network-adjacent to untrusted actors, the likelihood of exploitation is reduced.

The environment is affected if a Sonos Era 300 speaker is running Sonos S2 firmware version lower than 83.1-61240 and the device is network-adjacent to potential attackers who can send malicious HLS playlist 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.

dbcve · scoped
Upgrade available Upgrade to 83.1-61240 or later
Fixed in 83.1-61240
Interim mitigation

Since Sonos must release a firmware patch to address the root cause, immediate compensating controls should include network segmentation to restrict physical or logical access to the speaker's management interfaces, and monitoring for anomalous HLS traffic patterns until an official patch is available.

Recommended fix High confidence

S2 firmware version 83.1-61240 or later

  1. Open the Sonos app on a device connected to the same network as the Sonos Era 300
  2. Navigate to Settings > System > System Updates
  3. Check for available updates - the device should receive firmware 83.1-61240 or later
  4. If automatic updates are not enabled, tap 'Update Now' to initiate the firmware upgrade
  5. Wait for the update to complete (do not power off the speaker during the update process)
  6. After the update, verify the firmware version by going to Settings > System > About My System > Sonos Era 300

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in S2 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing3.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,050
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1050 — 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-1050 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