# CVE-2026-96425: Incorrect Permission Assignment for Critical Resource in lomiri-download-manager

> An incorrect DBus policy allows arbitrary users to execute commands as root, leading to privilege escalation in Lomiri download manager.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** Yes
- **Published:** 16 Oct 2026
- **Updated:** 18 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-96425, GHSA-xrrp-gpj2-96j9, UBUNTU-CVE-2026-96425

## What is CVE-2026-96425?

CVE-2026-96425 is a medium-severity vulnerability in UBports lomiri-download-manager, published on 16 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Incorrect DBus policy for lomiri-download-manager allows arbitrary user to run arbitrary command as root over DBus

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2026-96425?


## How do I fix CVE-2026-96425?

Apply the vendor's patch.

## Is CVE-2026-96425 being exploited?

There is no known exploitation of CVE-2026-96425 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-96425 and fix it if it is affected.

What it is: CVE-2026-96425 is a medium-severity vulnerability in UBports lomiri-download-manager, published on 16 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-96425 in the wild and no public exploit code.

Affected product: UBports lomiri-download-manager. 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-2026-96425/ (Markdown: https://insights.sbomify.com/CVE-2026-96425/index.md)
```

## Sources

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

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