dbcve.org
Radio Audio Streaming StackApplication · Sonicverse

CVE-2026-40089

CRITICAL · 9.9 CVSS v3.1 Published 2026-04-09
Fix available
A fix is available. Upgrade to 1.7.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
Sonicverse is a Self-hosted Docker Compose stack for live radio streaming. The Sonicverse Radio Audio Streaming Stack dashboard contains a Server-Side Request Forgery (SSRF) vulnerability in its API client (apps/dashboard/lib/api.ts). Installations created using the provided install.sh script (including the one‑liner bash <(curl -fsSL https://sonicverse.short.gy/install-audiostack)) are affected. In these deployments, the dashboard accepts user-controlled URLs and passes them directly to a server-side HTTP client without sufficient validation. An authenticated operator can abuse this to make arbitrary HTTP requests from the dashboard backend to internal or external systems. This vulnerability is fixed with commit cb1ddbacafcb441549fe87d3eeabdb6a085325e4.

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

Sonicverse Radio Audio Streaming Stack dashboard contains an SSRF vulnerability in apps/dashboard/lib/api.ts where user-supplied URLs are passed directly to a server-side HTTP client without validation. An authenticated operator can abuse this to make arbitrary HTTP requests from the backend to internal services or external systems.

MitigationUpdate to the version containing commit cb1ddbacafcb441549fe87d3eeabdb6a085325e4. If immediate patching is not feasible, implement network segmentation to restrict the dashboard container's outbound access to trusted endpoints only.

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
Radio Audio Streaming StackApplication
Affected:< 1.7.2

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L

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 installed Sonicverse Radio version
    Check the deployed version of Sonicverse Radio Audio Streaming Stack (check Docker image tag, package.json version field, or running service version endpoint)
    Affected if Installed version is below 1.7.2
  2. Verify dashboard API client is in use
    Confirm the dashboard component is deployed and accessible - the vulnerability exists in apps/dashboard/lib/api.ts
    Affected if Dashboard API functionality is exposed and accessible to authenticated operators
  3. Inspect URL validation in api.ts
    Review the file at apps/dashboard/lib/api.ts for server-side HTTP request handling and examine whether user-supplied URLs are validated before being passed to the HTTP client
    Affected if User-controlled URLs are passed to the HTTP client without sufficient validation or allowlist controls

You are affected if your deployed Sonicverse Radio Audio Streaming Stack version is below 1.7.2 and the dashboard API accepts user-controlled URLs without proper validation.

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 1.7.2 or later
Fixed in 1.7.2
Interim mitigation

Update to the version containing commit cb1ddbacafcb441549fe87d3eeabdb6a085325e4. If immediate patching is not feasible, implement network segmentation to restrict the dashboard container's outbound access to trusted endpoints only.

Recommended fix High confidence

1.7.2 or later

  1. Backup your current Sonicverse installation and configuration
  2. Pull the latest version of the Sonicverse Radio Audio Streaming Stack (version 1.7.2 or later)
  3. If using Docker Compose, update your docker-compose.yml to use the new version tag
  4. Re-deploy the dashboard container with: docker-compose up -d
  5. Verify the fix by reviewing the code changes in commit cb1ddbacafcb441549fe87d3eeabdb6a085325e4 in the apps/dashboard/lib/api.ts file
  6. Test that URL validation is properly implemented and user-controlled URLs cannot be used for SSRF attacks

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

Fix this in Radio Audio Streaming Stack Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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