# CVE-2024-35585: Auth bypass in MinKNOW

> Attackers can bypass authentication in MinKNOW by spoofing their source IP address, gaining unauthorized access to the sequencing control interface.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Sep 2026
- **Updated:** 2 Sep 2026
- **Also known as:** GHSA-46ch-vj4w-7pw8

## What is CVE-2024-35585?

CVE-2024-35585 is a high-severity authentication bypass vulnerability in Oxford Nanopore MinKNOW, published on 2 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Oxford Nanopore MinKNOW before 24.06 relies on a client's source IP address for authentication.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2024-35585?


## How do I fix CVE-2024-35585?

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

## Is CVE-2024-35585 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-35585 and fix it if it is affected.

What it is: CVE-2024-35585 is a high-severity authentication bypass vulnerability in Oxford Nanopore MinKNOW, published on 2 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-35585 in the wild and no public exploit code.

Affected product: Oxford Nanopore MinKNOW. 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-2024-35585/ (Markdown: https://insights.sbomify.com/CVE-2024-35585/index.md)
```

## Sources

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

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