# CVE-2025-61774: PyVista has Dependency Confusion Vulnerability in that leads to RCE

> Attackers can achieve remote code execution by publishing a malicious package with a higher version to PyPI, exploiting dependency confusion in PyVista.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2025
- **Updated:** 7 Oct 2025
- **Also known as:** DEBIAN-CVE-2025-61774, GHSA-xr7f-qcjc-63rv, UBUNTU-CVE-2025-61774

## What is CVE-2025-61774?

CVE-2025-61774 is a critical vulnerability in pyvista, published on 6 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PyVista provides 3D plotting and mesh analysis through an interface for the Visualization Toolkit (VTK). Version 0.46.3 of the PyVista Project is vulnerable to remote code execution via dependency confusion. Two pieces of code use`--extra-index-url`. But when `--extra-index-url` is used, pip always checks for the PyPI index first, and then the external index. One package listed in the code is not published in PyPI. If an attacker publishes a package with higher version in PyPI, the malicious code from the attacker controlled package may be pulled, leading to remote code execution and a supply chain attack. As of time of publication, a patched version is unavailable.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2025-61774 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61774 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-61774 is a critical vulnerability in pyvista, published on 6 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61774 exists.

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

## Sources

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

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