# CVE-2026-91841: Command injection in NetworkManager-vpnc

> Local attackers can escalate privileges to root by injecting newlines into CA file paths in NetworkManager-vpnc, enabling arbitrary command execution.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 25 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-91841, GHSA-w3p6-vc7r-vcv4, UBUNTU-CVE-2026-91841

## What is CVE-2026-91841?

CVE-2026-91841 is a high-severity command injection vulnerability in GNOME NetworkManager-vpnc, published on 25 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw was found in NetworkManager-vpnc, a VPN plugin for NetworkManager. A local unprivileged user can exploit this vulnerability by injecting a newline character into the CA-File path. This manipulation allows the user to execute arbitrary commands as the root user, leading to local privilege escalation.

Weakness: CWE-93 (Improper Neutralization of CRLF Sequences)

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


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

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

## Is CVE-2026-91841 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-91841 is a high-severity command injection vulnerability in GNOME NetworkManager-vpnc, published on 25 Sep 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-91841 in the wild and no public exploit code.

Affected product: GNOME NetworkManager-vpnc. 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-91841/ (Markdown: https://insights.sbomify.com/CVE-2026-91841/index.md)
```

## Sources

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

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