# CVE-2025-13131: Sonarr Service Sonarr.Console.exe default permission

> Local attackers can escalate privileges if the Sonarr service is manually configured to run with high-privilege accounts due to insecure default permissions.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Nov 2025
- **Updated:** 14 Nov 2025
- **Also known as:** GHSA-h3rm-rxwj-hfmw

## What is CVE-2025-13131?

CVE-2025-13131 is a high-severity vulnerability in Sonarr, published on 13 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in Sonarr 4.0.15.2940. The impacted element is an unknown function of the file C:\ProgramData\Sonarr\bin\Sonarr.Console.exe of the component Service. Performing manipulation results in incorrect default permissions. The attack is only possible with local access. The vendor confirms this vulnerability but classifies it as a "low severity issue due to the default service user being used as it would either require someone to intentionally change the service to a highly privileged account or an attacker would need an admin level account". It is planned to fix this issue in the next major release v5.

Weakness: CWE-276 (Incorrect Default Permissions), CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2025-13131?


## How do I fix CVE-2025-13131?

No fix has been published for CVE-2025-13131 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-13131 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-13131 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-13131 and fix it if it is affected.

What it is: CVE-2025-13131 is a high-severity vulnerability in Sonarr, published on 13 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-13131 exists.

Affected product: Sonarr. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-13131/ (Markdown: https://insights.sbomify.com/CVE-2025-13131/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-13131
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-13131
- OSV: https://osv.dev/vulnerability/CVE-2025-13131

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-13131/
Summaries are generated and may contain mistakes; the official description above is the record.