Sequencing denial of service via token-file lock
Published Oct 23, 2025 · Updated Oct 23, 2025
Denial of service in Oxford Nanopore Technologies MinKNOW before 24.11 allows local users to block sequencing via a token-file lock. During startup, MinKNOW creates a local authentication-token file in a directory accessible to all users and does not recover when flock prevents token generation. A low-privileged local user or process can prevent command execution on the sequencer, blocking sequencing operations without reading or altering data.
Summary
What happened
Denial of service in Oxford Nanopore Technologies MinKNOW before 24.11 allows local users to block sequencing via a token-file lock. During startup, MinKNOW creates a local authentication-token file in a directory accessible to all users and does not recover when flock prevents token generation. A low-privileged local user or process can prevent command execution on the sequencer, blocking sequencing operations without reading or altering data.
The record
- CVE
- CVE-2025-10937
- Published
- Oct 23, 2025
- Updated
- Oct 23, 2025
- Vendor
- Oxford Nanopore Technologies
- Product
- MinKNOW
- Classifications
- CWE-754, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 23, 2025CVE publishedPublication date reported by the CVE source.
- Oct 23, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <24.11
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo