dbcve.org
SonarrApplication

CVE-2026-30976

HIGH · 7.5 CVSS v3.1 Published 2026-03-25
Fix available
A fix is available. Upgrade to 4.0.17.2950 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable 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
Sonarr is a PVR for Usenet and BitTorrent users. In versions on the 4.x branch prior to 4.0.17.2950, an unauthenticated remote attacker can potentially read any file readable by the Sonarr process. These include application configuration files (containing API keys and database credentials), Windows system files, and any user-accessible files on the same drive This issue only impacts Windows systems; macOS and Linux are unaffected. Files returned from the API were not limited to the directory on disk they were intended to be served from. This problem has been patched in 4.0.17.2950 in the nightly/develop branch or 4.0.17.2952 for stable/main releases. It's possible to work around the issue by only hosting Sonarr on a secure internal network and accessing it via VPN, Tailscale or similar solution outside that network.

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 path traversal vulnerability in Sonarr's API on Windows that allows unauthenticated remote attackers to read any file accessible by the Sonarr process through improper path validation, exposing sensitive configuration files with API keys and database credentials, as well as Windows system files.

MitigationUpgrade Sonarr to version 4.0.17.2952 or later. As an interim measure, restrict network access by hosting Sonarr on a secure internal network accessible only via VPN or similar solutions.

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
SonarrApplication
Affected:>= 4.0.0.741, < 4.0.17.2950

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 Sonarr version
    Locate Sonarr's version number in the application UI under System > Status, or check the Windows service information via Services.msc or the application's log files
    Affected if installed version is 4.0.0.741 or higher but lower than 4.0.17.2950
  2. Confirm Windows platform
    Verify that the Sonarr instance is running on a Windows operating system by checking the host system or service properties
    Affected if Sonarr is running on Windows
  3. Verify API accessibility
    Determine if the Sonarr API endpoint (default port 8989) is listening on a network-accessible IP address rather than localhost only, using netstat or by checking the configuration binding
    Affected if API port is bound to a non-localhost interface and accessible from network

A user is affected if Sonarr version falls within 4.0.0.741 to 4.0.17.2949, is running on Windows, and has its API port network-accessible.

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

Upgrade Sonarr to version 4.0.17.2952 or later. As an interim measure, restrict network access by hosting Sonarr on a secure internal network accessible only via VPN or similar solutions.

Recommended fix High confidence

4.0.17.2952 (stable/main) or 4.0.17.2950 (nightly/develop)

  1. Back up your Sonarr configuration and database before upgrading
  2. Stop the Sonarr service
  3. Download Sonarr version 4.0.17.2952 (stable/main) or 4.0.17.2950 (nightly/develop) from the official Sonarr GitHub releases
  4. Install the new version, overwriting the existing installation
  5. Start the Sonarr service
  6. Verify the Sonarr web interface is accessible and functioning normally
  7. Confirm the version number in Sonarr settings shows 4.0.17.2952 or later

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

Fix this in Sonarr Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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