# CVE-2026-41958: Path traversal in visidata

> A path traversal in VisiData allows attackers to write arbitrary files via a crafted zip file, requiring user interaction to open a malicious URL.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-mfmr-282v-wvc7, UBUNTU-CVE-2026-41958

## What is CVE-2026-41958?

CVE-2026-41958 is a medium-severity path traversal vulnerability in visidata, published on 7 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A path traversal vulnerability exists in the unzip_http RemoteZipFile extract functionality of VisiData (version(s): dev (commit 38b21f78)). A specially crafted .zip file can lead to arbitrary file write. An attacker can provide a crafted URL to trigger this vulnerability.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-41958 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41958 is a medium-severity path traversal vulnerability in visidata, published on 7 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-41958 in the wild and no public exploit code.

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

## Sources

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

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