Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain local shell account on shared HPC node
-
DeliveryIdentify victim who ran nextflow auth login
-
ExploitTraverse world-executable home directory
-
ExecutionRead world-readable seqera-auth.config
-
PersistExtract Seqera Platform bearer token
-
ImpactImpersonate victim against Seqera Platform API
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V13 - Configuration Default permission hardening
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires all of the following to be true simultaneously: (1) the victim has run |
| Impact | The NVD CVSS 3.1 vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N (score 5.5) accurately characterizes the threat: local access is mandatory, no privilege escalation is needed beyond a standard shell account, exploitation is low-complexity, and the sole impact is complete confidentiality loss of the stored credential. No EPSS score was supplied in the available intelligence data, so probabilistic exploitation likelihood cannot be quantified from this analysis. The vulnerability is not listed in the CISA KEV catalog, and no public exploit code has been identified at time of analysis - these two signals suggest opportunistic mass exploitation is not currently occurring. However, the practical risk in HPC and shared research infrastructure is meaningfully higher than the raw score implies: home directories on Linux HPC clusters are commonly world-traversable (mode 755 or 711 by default), Nextflow's primary user base operates on exactly these systems, and exploitation requires zero tooling beyond standard shell access. The 'Privilege Escalation' tag is appropriate - a low-privileged local user effectively acquires Seqera Platform access scoped to the victim's token. The flaw is irrelevant on single-user systems and headless CI runners, which materially narrows real-world exposure. |
| Exploit ScenarioDerived | A low-privileged user on a shared bioinformatics HPC login node - where dozens of researchers share a single system to submit Nextflow jobs - notices that a colleague's home directory is world-traversable. The attacker runs |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 25, 2026
Insecure default file permissions in Nextflow's auth login command expose Seqera Platform OIDC bearer tokens to any local user on shared POSIX systems running affected versions 25.09.2-edge through 26.04.1. The credential file seqera-auth.config is written via Java NIO without explicit permission bits, landing at mode 0644 under the typical umask 022, making it world-readable on HPC login nodes, shared workstations, and jump hosts - exactly the infrastructure where Nextflow is most commonly deployed. No public exploit has been identified at time of analysis and this vulnerability is not currently in the CISA KEV catalog, but the attack requires only a standard local account and trivial filesystem read, making it a practical lateral-movement primitive in multi-tenant research computing environments.
RemediationAI
Upgrade to Nextflow 25.10.6 (25.x branch) or 26.04.3 (26.x branch); these releases apply mode 0600 to seqera-auth.config immediately after writing and re-apply the restriction on every subsequent login, also correcting any pre-existing world-readable copy created by a vulnerable version. After upgrading, previously stored tokens must be treated as disclosed: run nextflow auth logout, revoke the token in the Seqera Platform UI, then re-authenticate with nextflow auth login to generate a fresh credential written with correct permissions. For immediate pre-patch mitigation on vulnerable systems, run chmod 600 "${NXF_HOME:-$HOME/.nextflow}/seqera-auth.config" and chmod 700 "${NXF_HOME:-$HOME/.nextflow}" - this tightens existing exposure but does not prevent recurrence if nextflow auth login is re-run on a vulnerable version, as the file will be recreated world-readable. A persistent workaround that avoids disk-based credential storage entirely is to supply the token via the TOWER_ACCESS_TOKEN environment variable rather than using nextflow auth login; this eliminates the file-based exposure but requires secure injection of the variable (e.g., via a CI secrets manager or PAM environment configuration), which may be operationally complex in HPC settings. See the advisory at https://github.com/nextflow-io/nextflow/security/advisories/GHSA-92qf-fcph-v5wr.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 3 packages in maven, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Nextflow is a bioinformatics workflow orchestration engine distributed as the Maven artifact io.nextflow:nextflow. Its Seqera Platform integration authenticates via OIDC and, when nextflow auth login is run interactively, persists the resulting bearer token to ${NXF_HOME:-~/.nextflow}/seqera-auth.config. The file is created through Java NIO's default file-creation path, which does not specify POSIX permission attributes - the resulting permissions are therefore determined entirely by the process umask. Under the near-universal default of umask 022, this produces mode 0644 (owner rw, group r, world r). CWE-276 (Incorrect Default Permissions) is the precise root cause: the application fails to enforce least-privilege file permissions when persisting sensitive credentials, violating the principle that credential stores must be owner-readable only (mode 0600). The CPE data confirms the affected artifact is pkg:maven/io.nextflow:nextflow across two release trains.
Know when Java gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Local low-privileged shell access required to read the credential file; sole measurable impact is confidentiality of the stored bearer token with no integrity or availability effect.
Primary rating from Vendor (https://github.com/nextflow-io/nextflow).
CVSS VectorVendor: https://github.com/nextflow-io/nextflow
DescriptionCVE.org
Impact
nextflow auth login persists Seqera Platform OIDC tokens to ${NXF_HOME:-~/.nextflow}/seqera-auth.config. The file is created via Java NIO without specifying file permissions, so under the default umask 022 it lands at mode 0644 (world-readable).
On a multi-user POSIX host - typically an HPC login node, shared workstation, or jump host - any local user able to traverse the victim's home directory can read the file and obtain a valid Platform bearer token, enabling impersonation against Seqera Platform within the token's scope.
Single-user systems and headless CI runners, which do not invoke the interactive login flow, are not affected.
Affected versions: 25.09.2-edge through 26.04.1.
Patches
Fixed in <PATCHED_VERSION>. The patched code applies mode 0600 to seqera-auth.config immediately after writing it, and re-applies on every subsequent login so any pre-existing world-readable copy left by an earlier version is tightened.
Tokens previously stored in the file must be treated as disclosed. After upgrading, run nextflow auth logout, revoke the token in the Seqera Platform UI, and run nextflow auth login again.
Workarounds
Restrict the file and its parent directory:
chmod 600 "${NXF_HOME:-$HOME/.nextflow}/seqera-auth.config" chmod 700 "${NXF_HOME:-$HOME/.nextflow}"
Alternatively, supply the Platform token via the TOWER_ACCESS_TOKEN environment variable instead of running nextflow auth login.
References
- https://cwe.mitre.org/data/definitions/276.html
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Oracle Java SE 7 Update 6 and earlier contains multiple sandbox bypass vulnerabilities via the ClassFinder and forName m
Remote code execution in IBM Sterling B2B Integrator, Sterling Integrator, and Tivoli Common Reporting allows unauthenti
Java Runtime Environment sandbox bypass via incorrect image channel verification in 2D component allows remote unauthent
Oracle Java SE JDK/JRE 7 and 6 Update 27 and earlier allows remote code execution with complete system compromise throug
JBoss Seam 2 in Red Hat JBoss EAP 4.3.0 fails to sanitize JBoss Expression Language inputs, allowing remote attackers to
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 update 4 and earlier, 6 up
Multiple vulnerabilities in Oracle Java 7 before Update 11 allow remote attackers to execute arbitrary code by (1) using
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 2 and earlier, 6 Up
The WLS Security component in Oracle WebLogic Server 10.3.6.0, 12.1.2.0, 12.1.3.0, and 12.2.1.0 allows remote attackers
Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 7 and earlier allow
Remote unauthenticated attackers can execute arbitrary code on Adobe ColdFusion servers through Java deserialization fla
The ExceptionDelegator component in Apache Struts before 2.2.3.1 interprets parameter values as OGNL expressions during
EUVD-2026-78578
GHSA-92qf-fcph-v5wr
NVD
CVE.org
EPSS
Exploit-DB