# CVE-2025-66005: Lack of Authentication in the InputManager D-Bus interface

> Local attackers can exploit missing authorization in InputPlumber's D-Bus interface to cause denial of service, leak information, or escalate privileges.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Jan 2026
- **Updated:** 14 Jan 2026
- **Also known as:** GHSA-2j9c-mj82-5gj2

## What is CVE-2025-66005?

CVE-2025-66005 is a high-severity missing authorization vulnerability in https://github.com/ShadowBlip inputplumber, published on 14 Jan 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Lack of authorization of the InputManager D-Bus interface in
InputPlumber versions before v0.63.0 can lead to local Denial-of-Service,
information leak or even privilege escalation in the context of the
currently active user session.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2025-66005 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-66005 is a high-severity missing authorization vulnerability in https://github.com/ShadowBlip inputplumber, published on 14 Jan 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-66005 in the wild and no public exploit code.

Affected product: https://github.com/ShadowBlip inputplumber. 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-66005/ (Markdown: https://insights.sbomify.com/CVE-2025-66005/index.md)
```

## Sources

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

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