# CVE-2025-56513: Supply chain in n/a

> An attacker could hijack software updates to deliver malicious executables, though the vendor disputes the vulnerability's existence.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Sep 2025
- **Updated:** 11 May 2026
- **Also known as:** GHSA-wr4m-f8q9-97q2

## What is CVE-2025-56513?

CVE-2025-56513 is a critical vulnerability in n/a, published on 30 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NiceHash QuickMiner 6.12.0 perform software updates over HTTP without validating digital signatures or hash checks. An attacker capable of intercepting or redirecting traffic to the update url and can hijack the update process and deliver arbitrary executables that are automatically executed, resulting in full remote code execution. This constitutes a critical supply chain attack vector. NOTE: the Supplier reports that the existence of an http://update.nicehash.com URL is a fabrication, and that there is no other use of HTTP (rather than HTTPS).

Weakness: CWE-494 (Download of Code Without Integrity Check)

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

It affects 1 product.


Products: Nicehash Quickminer.

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

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

## Is CVE-2025-56513 being exploited?

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

Public exploit code:

- Critical supply-chain vulnerability research on NiceHash QuickMiner update mechanism (CVE-2025-56513). Includes technical analysis, attack scenarios, impact assessment, and remediation guidance. (github_poc): https://github.com/psycho-prince/CVE-2025-56513-NiceHash-Update-Chain-Compromise

## Fix prompt for AI coding agents

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

What it is: CVE-2025-56513 is a critical vulnerability in n/a, published on 30 Sep 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-56513 exists.

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

## Sources

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

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