dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2025-66005

HIGH · 8.5 CVSS v4.0 Published 2026-01-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
88/100
Remediation priority · High
No privileges

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
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.

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

InputPlumber's InputManager D-Bus interface lacks authorization checks in versions before v0.63.0, allowing any local user to invoke D-Bus methods without proper authentication. This enables local attackers to cause denial-of-service, leak sensitive information, or escalate privileges within the active user session.

MitigationUpgrade InputPlumber to v0.63.0 or later to obtain the authorization checks. Alternatively, restrict D-Bus access through system policy files until the upgrade can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Local
Complexity
Low
Privileges
None
Authentication
X
User interaction
P
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 if InputPlumber is installed
    Query your package manager for InputPlumber (e.g., `dpkg -l | grep inputplumber`, `rpm -qa | grep inputplumber`, or check `/usr/bin/inputplumber` existence)
    Affected if InputPlumber is present on the system
  2. Determine installed InputPlumber version
    Run `inputplumber --version` or check via package manager (`dpkg -s inputplumber`, `rpm -qi inputplumber`)
    Affected if Version is earlier than v0.63.0 (e.g., v0.62.x, v0.61.x, etc.)
  3. Verify D-Bus service availability
    Query D-Bus for InputPlumber service: `dbus-send --session --dest=com.inputplumber.InputManager --type=method_call --print-reply /com/inputplumber/InputManager org.freedesktop.DBus.Introspectable.Introspect` or check `busctl list | grep inputplumber`
    Affected if The D-Bus interface is exposed and responds to method calls
  4. Confirm lack of authorization enforcement
    Attempt a non-privileged D-Bus method call from a secondary user account (e.g., `dbus-send --session --dest=com.inputplumber.InputManager --type=method_call /com/inputplumber/InputManager <any_method>`)
    Affected if The call succeeds without authentication or authorization failure

A user is affected if InputPlumber is installed with a version earlier than v0.63.0 AND the D-Bus interface is exposed and callable without authentication.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade InputPlumber to v0.63.0 or later to obtain the authorization checks. Alternatively, restrict D-Bus access through system policy files until the upgrade can be applied.

Recommended fix High confidence

InputPlumber v0.63.0 or later

  1. Check the currently installed version of InputPlumber using your package manager (e.g., `rpm -q inputplumber` or `dpkg -l inputplumber`)
  2. Upgrade InputPlumber to version v0.63.0 or later using your package manager (e.g., `sudo zypper update inputplumber` on openSUSE/SUSE or `sudo apt-get install inputplumber` depending on available packages)
  3. After upgrading, verify the new version is installed correctly
  4. Restart the InputPlumber service or D-Bus session to ensure the patched version is running (e.g., `sudo systemctl restart inputplumber` or log out/in of the session)

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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