{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-30976 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-30976 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-30976 is a high-severity path traversal vulnerability in Sonarr, published on 25 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-30976 and fix it if it is affected.\n\nWhat it is: CVE-2026-30976 is a high-severity path traversal vulnerability in Sonarr, published on 25 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-30976 in the wild and no public exploit code.\n\nAffected product: Sonarr. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-30976/ (Markdown: https://insights.sbomify.com/CVE-2026-30976/index.md)","id":"CVE-2026-30976","markdown":"https://insights.sbomify.com/CVE-2026-30976/index.md","name":"CVE-2026-30976","record":{"aliases":["GHSA-h393-v5hm-6h8f"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Sonarr PVR application","requires_auth":"none","summary":"Unauthenticated attackers can read arbitrary files on Windows systems via path traversal, exposing sensitive configuration and system data.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"sonarr","vendor":"sonarr"}],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Sonarr Path Traversal vulnerability","id":"CVE-2026-30976","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"RenderBlocking has Stored XSS in renderblocking-css with Inline Assets mode","id":"CVE-2026-30977"},"packages":[],"prev":{"headline":"Sonarr Authentication Bypass vulnerability","id":"CVE-2026-30975"},"products":["Sonarr"],"published":"2026-03-25","related":[{"cvss_score":8.1,"headline":"Sonarr Authentication Bypass vulnerability","id":"CVE-2026-30975","kev_date_added":null,"published":"2026-03-25"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-26","vendors":["Sonarr"]},"summary":"Unauthenticated attackers can read arbitrary files on Windows systems via path traversal, exposing sensitive configuration and system data.","url":"https://insights.sbomify.com/CVE-2026-30976/"}