# CVE-2025-14338: Polkit authentication dis isabled by default in inputplumber

> Attackers can bypass Polkit authentication due to a race condition and default disabled state, leading to privilege escalation in InputPlumber.

- **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-fcpw-6r74-grvh

## What is CVE-2025-14338?

CVE-2025-14338 is a high-severity authentication bypass 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

Polkit authentication dis isabled by default and a race
condition in the Polkit authorization check in versions before v0.69.0 can
lead to the same issues as in CVE-2025-66005.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2025-14338 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14338 is a high-severity authentication bypass 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-14338 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-14338/ (Markdown: https://insights.sbomify.com/CVE-2025-14338/index.md)
```

## Sources

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

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