dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2026-44482

CRITICAL · 9.6 CVSS v3.1 Published 2026-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

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
soundcloud-rpc is a SoundCloud Client with Discord Rich Presence, Dark Mode, Last.fm and AdBlock support. Prior to 0.1.8, a track title containing an HTML payload executed locally in the Electron app. This means attacker-controlled SoundCloud track metadata can lead to local command execution on the user's machine. The application exposes a preload API (window.soundcloudAPI.sendTrackUpdate) to the remote SoundCloud page. Track metadata from SoundCloud is trusted and forwarded through IPC into the Electron main process. The app later renders that metadata as raw HTML inside privileged Electron views that have Node.js integration enabled. This vulnerability is fixed in 0.1.8.

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

This is a stored XSS-to-RCE vulnerability in the soundcloud-rpc Electron application. Attackers controlling SoundCloud track metadata can inject malicious HTML/JavaScript that gets passed through the exposed preload API (window.soundcloudAPI.sendTrackUpdate) via IPC to the main process, then rendered as raw HTML in privileged Electron renderer views with Node.js integration enabled, enabling arbitrary command execution on the victim's machine.

MitigationUpgrade to version 0.1.8 or later, which sanitizes track metadata before rendering and/or disables Node.js integration in renderer processes. As a temporary workaround, avoid using the application until upgraded.

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

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
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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. Check if soundcloud-rpc is installed
    Locate the soundcloud-rpc application on the system. Check common installation paths such as Program Files (Windows), /Applications (macOS), or ~/.local/share (Linux). Look for the application executable or package.
    Affected if The application is present on the system
  2. Identify the installed version
    Open the application's main file (typically package.json or the app's metadata file within the installation directory) and locate the version field. Alternatively, run 'soundcloud-rpc --version' or check the application's 'About' menu if available.
    Affected if The version is lower than 0.1.8 (e.g., 0.1.7, 0.1.6, etc.)
  3. Inspect Electron renderer configuration
    Examine the main.js or main process JavaScript file for webPreferences configuration. Look for the 'nodeIntegration' and 'contextIsolation' settings. Also check any .js or .json files in the resources or config directories for Electron security settings.
    Affected if nodeIntegration is set to true or not explicitly set to false in the renderer configuration
  4. Verify preload API exposure
    Locate the preload script file (usually preload.js or similar in the resources/app directory). Search for 'soundcloudAPI' and the 'sendTrackUpdate' method to confirm the vulnerable IPC channel exists.
    Affected if The preload script exposes window.soundcloudAPI.sendTrackUpdate without input sanitization checks

The system is affected if soundcloud-rpc is installed with a version prior to 0.1.8 and the application has Node.js integration enabled in its renderer process configuration.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 0.1.8 or later, which sanitizes track metadata before rendering and/or disables Node.js integration in renderer processes. As a temporary workaround, avoid using the application until upgraded.

Recommended fix High confidence

0.1.8

  1. 1. Check the currently installed version of soundcloud-rpc
  2. 2. Upgrade soundcloud-rpc to version 0.1.8 or later by reinstalling or updating the package

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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