critical CVSS 9.9

CVE-2026-40089·Docker vulnerability

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.

Severity
critical
Software
Docker
Fixed in
1.7.2
Published
2026-04-09

Affected versions

Until: 1.7.2

Fixed in: 1.7.2

How to fix this CVE

Update Docker to version 1.7.2 or later to patch the SSRF vulnerability in the Sonicverse Radio Audio Streaming Stack dashboard. The vulnerability allows authenticated operators to make arbitrary HTTP requests from the dashboard backend by bypassing URL validation in the API client. Immediately apply this update to all affected installations, particularly those deployed via the official install.sh script.

sudo dnf update docker-ce -y && sudo systemctl restart docker

Defensia detects this vulnerability

What an exploitation attempt looks like

Sample log line indicative of exploitation attempts:

POST /api/[^\s]+ with user-controlled 'url' parameter pointing to internal IP ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) or external domains; response time anomalies indicating backend HTTP requests; dashboard logs containing 'fetch|curl|request' followed by internal service names or metadata endpoints

WAF mitigation (if patching is not yet possible)

Add this rule to your WAF to block exploitation attempts while you schedule the patch. 

Implement WAF rules to block API requests where the 'url' parameter contains internal IP addresses, private network CIDR blocks, localhost variants (127.0.0.1, ::1), or cloud metadata endpoints (169.254.169.254, 10.0.0.0/8). Enforce strict URL schema validation (http/https only) and maintain an allowlist of permitted target domains if URL requests are business-critical.

How to check if you are affected

  1. Check installed Docker version: docker --version or docker version --format '{{.Server.Version}}'
  2. Verify Sonicverse dashboard is running: docker ps | grep -i sonicverse or check docker-compose ps in the deployment directory
  3. Examine dashboard API logs for unusual HTTP requests: docker logs <container_name> | grep -i 'http\|request\|url' to identify outbound requests to unexpected destinations
  4. Confirm patch applied by checking the git commit hash: git log --oneline | head -5 should show cb1ddbacafcb441549fe87d3eeabdb6a085325e4 or later in the Sonicverse repository

FAQ

What is CVE-2026-40089?

CVE-2026-40089 is a Server-Side Request Forgery (SSRF) vulnerability in the Sonicverse Radio Audio Streaming Stack dashboard that allows authenticated operators to bypass URL validation and make arbitrary HTTP requests from the backend server to internal or external systems.

Is CVE-2026-40089 being actively exploited?

According to CISA, CVE-2026-40089 is not currently listed in the Known Exploited Vulnerabilities (KEV) catalog and no public exploits are available, though the vulnerability is critical in severity.

What versions of Docker are affected by CVE-2026-40089?

Sonicverse versions up to and including 1.7.1 are affected when deployed with Docker; version 1.7.2 and later contain the fix.

How do I check if my server is vulnerable to CVE-2026-40089?

Run 'docker ps --format "table {{.Names}}\t{{.Image}}"' to list running containers and identify Sonicverse deployments, then check the image tag against version 1.7.2 or later.

Does Defensia detect CVE-2026-40089?

Yes — Defensia's CVE advisory scanner compares installed Docker and containerized application versions against the NVD database. If Sonicverse is detected on a monitored server, CVE-2026-40089 will appear in your dashboard with remediation steps.

Related Docker CVEs

CVE-2026-57572CVSS 10Crawl4AI is an open-source LLM-friendly web crawler and scraper. Prior to 0.9.0, the Docker API server accepted request-supplied browser_config.extra_args, which flowed into Chromium's launch arguments. An attacker could inject Chromium switches that replace a child-process launch command together with --no-zygote, causing Chromium to fork or exec an attacker-controlled command as the container's runtime user. The Docker API is unauthenticated by default, so a single request yields arbitrary command execution. This issue is fixed in version 0.9.0.
CVE-2026-26216CVSS 10Crawl4AI versions prior to 0.8.0 contain a remote code execution vulnerability in the Docker API deployment. The /crawl endpoint accepts a hooks parameter containing Python code that is executed using exec(). The __import__ builtin was included in the allowed builtins, allowing unauthenticated remote attackers to import arbitrary modules and execute system commands. Successful exploitation allows full server compromise, including arbitrary command execution, file read and write access, sensitive data exfiltration, and lateral movement within internal networks.
CVE-2026-44329CVSS 10free5GC is an open-source implementation of the 5G core network. Prior to 4.2.2, free5GC's SMF mounts the UPI management route group without OAuth2/bearer-token authorization middleware. A network attacker who can reach SMF on the SBI can hit UPI endpoints with no Authorization header at all, and the requests reach the SMF business handlers. In the running Docker lab this was directly demonstrated for read (GET /upi/v1/upNodesLinks), write (POST /upi/v1/upNodesLinks with attacker-controlled UP-node and link payload), and delete (DELETE /upi/v1/upNodesLinks/{nodeID}) operations. This vulnerability is fixed in 4.2.2.
CVE-2026-53576CVSS 10Kestra is an open-source, event-driven orchestration platform. Prior to 1.0.45 and 1.3.21, the authentication filter for the REST API (@Filter("/api/v1/**")) treats any request whose path ends in /configs as the public instance-config endpoint and forwards it without a credential check. kestra addresses its resources by URL path segments that the caller chooses (/api/v1/{tenant}/flows/{namespace}, /api/v1/{tenant}/executions/{namespace}/{id}, /api/v1/{tenant}/namespaces/{namespace}/kv/{key}). An anonymous caller picks the literal configs as the final segment, and the request bypasses Basic-Auth entirely. Because the bypass reaches the flow-create and execution-trigger routes, an unauthenticated caller creates a flow containing a Shell or Process task and runs it. The task executes as root inside the kestra container. The official docker-compose.yml mounts /var/run/docker.sock, so root in the container reaches the host Docker daemon. This vulnerability is fixed in 1.0.45 and 1.3.21.
CVE-2026-33587CVSS 10Lack of user input sanitisation in Open Notebook v1.8.3 allows the application user to execute Python code (and subsequently OS commands) on the docker container via Server-Side Template Injection (SSTI) for user-created transformations.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-40089. Free for 1 server.

Get started free