CVE-2026-48722: nextflow · Incorrect Default Permissions
Affects nextflowSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium : upgrade to 26.04.3 or 25.10.6 when convenient.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-09-17.
- Patch
- Available – fixed in 26.04.3, 25.10.6
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 15 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade nextflow to 26.04.3 or 25.10.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| nextflow-ionextflow | Affected
| Fixed in
|
| nextflow-ionextflow | Affected
| Fixed in
|
Description
Nextflow is a DSL for data-driven computational pipelines. From 25.09.2-edge until 25.10.6 and 26.04.3, nextflow auth login writes Seqera Platform OIDC bearer tokens to ${NXF_HOME:-~/.nextflow}/seqera-auth.config through AuthCommandImpl.writeConfig in plugins/nf-tower/src/main/io/seqera/tower/plugin/auth/AuthCommandImpl.groovy without setting restrictive file permissions, allowing the default umask 022 to create the file with mode 0644. On a multi-user POSIX host, a local user who can traverse the victim's home directory can read seqera-auth.config and impersonate the victim against Seqera Platform within the token's scope. Single-user systems and headless CI runners that do not use the interactive login flow are not affected. This issue is fixed in 25.10.6 and 26.04.3.
References
- github.com/nextflow-io/nextflow/security/advisories/GHSA-92qf-fcph-v5wr (opens in a new tab)
- github.com/nextflow-io/nextflow/pull/7182 (opens in a new tab)
- github.com/nextflow-io/nextflow/commit/41a5f24afec8a6e9769a24cae5e08b5462fbfdc1 (opens in a new tab)
- github.com/nextflow-io/nextflow/commit/a2813c610a3e7f13d7a0a0b1b543b7ad47586eaa (opens in a new tab)
- github.com/nextflow-io/nextflow/releases/tag/v25.10.6 (opens in a new tab)
- github.com/nextflow-io/nextflow/releases/tag/v26.04.3 (opens in a new tab)