Nextflow: Incorrect default permissions in the nextflow auth login command
cve-program · CVE-2026-48722
PublishedNextflow 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.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-48722 · CVE overview and exploitation status
cve-program · CVE-2026-48722
- https://github.com/nextflow-io/nextflow/security/advisories/GHSA-92qf-fcph-v5wr
- https://github.com/nextflow-io/nextflow/pull/7182
- https://github.com/nextflow-io/nextflow/commit/41a5f24afec8a6e9769a24cae5e08b5462fbfdc1
- https://github.com/nextflow-io/nextflow/commit/a2813c610a3e7f13d7a0a0b1b543b7ad47586eaa
- https://github.com/nextflow-io/nextflow/releases/tag/v25.10.6
- https://github.com/nextflow-io/nextflow/releases/tag/v26.04.3
Related changes
Linked by CVE identifierNo related changes are available here.