Skip to main content

Nextflow CVE-2026-48722

| EUVDEUVD-2026-78578 MEDIUM
Incorrect Default Permissions (CWE-276)
2026-06-25 https://github.com/nextflow-io/nextflow GHSA-92qf-fcph-v5wr
5.5
CVSS 3.1 · Vendor: https://github.com/nextflow-io/nextflow
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain local shell account on shared HPC node
  2. Delivery
    Identify victim who ran nextflow auth login
  3. Exploit
    Traverse world-executable home directory
  4. Execution
    Read world-readable seqera-auth.config
  5. Persist
    Extract Seqera Platform bearer token
  6. Impact
    Impersonate 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 nextflow auth login at least once on a Nextflow version between 25.09.2-edge and 26.04.1, generating a seqera-auth.config file; (2) the attacker holds a local shell account on the same multi-user POSIX host; (3) the victim's home directory is world-traversable (execute bit set for others - mode 711 or 755, which is the default on most Linux distributions and HPC systems). Exploitation is blocked when: the home directory is mode 700 (not world-traversable, making the file unreachable even though it is world-readable); the victim exclusively uses the TOWER_ACCESS_TOKEN environment variable and never invokes nextflow auth login; or the system is single-user or a headless CI runner where the interactive auth flow is never invoked. The file permission flaw does not affect the Seqera Platform service itself - it is purely a local credential-theft primitive on the client host.

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 cat ~victim/.nextflow/seqera-auth.config and immediately obtains a valid Seqera Platform bearer token requiring no special tools or privilege. Using the token in an HTTP Authorization header, the attacker authenticates to Seqera Platform as the victim, gaining access to proprietary genomics pipelines, datasets, compute quotas, and organizational resources within the token's scope.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

nextflow 25.09.2-edge, < 25.10.6
nextflow 25.11.0-edge, < 26.04.3

Affected Packages

maven io.nextflow:nextflow fix: 25.10.6, 26.04.3
euvd nextflow_25_09_2_edge fix: 25.10.6
euvd nextflow_25_11_0_edge fix: 26.04.3

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

Vendor (https://github.com/nextflow-io/nextflow) PRIMARY 5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
vuln.today AI 5.5 MEDIUM

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.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (https://github.com/nextflow-io/nextflow).

CVSS VectorVendor: https://github.com/nextflow-io/nextflow

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

EPSS Score
0.1%
Top 99% exploitable
Prevalence
Low
niche bioinformatics workflow engine, primarily deployed in academic and research HPC environments
Threat Intel
1
1 source
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation· derived
None
System Exposure· derived
Small
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

28
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +28
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

More in Java

View all
CVE-2012-4681 CRITICAL POC
9.8 Aug 28

Oracle Java SE 7 Update 6 and earlier contains multiple sandbox bypass vulnerabilities via the ClassFinder and forName m

CVE-2015-7450 CRITICAL POC
9.8 Jan 02

Remote code execution in IBM Sterling B2B Integrator, Sterling Integrator, and Tivoli Common Reporting allows unauthenti

CVE-2013-2465 CRITICAL POC
9.8 Jun 18

Java Runtime Environment sandbox bypass via incorrect image channel verification in 2D component allows remote unauthent

CVE-2011-3544 CRITICAL POC
9.8 Oct 19

Oracle Java SE JDK/JRE 7 and 6 Update 27 and earlier allows remote code execution with complete system compromise throug

CVE-2010-1871 HIGH POC
8.8 Aug 05

JBoss Seam 2 in Red Hat JBoss EAP 4.3.0 fails to sanitize JBoss Expression Language inputs, allowing remote attackers to

CVE-2012-1723 CRITICAL POC
9.8 Jun 16

Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 update 4 and earlier, 6 up

CVE-2013-0422 CRITICAL POC
9.8 Jan 10

Multiple vulnerabilities in Oracle Java 7 before Update 11 allow remote attackers to execute arbitrary code by (1) using

CVE-2012-0507 CRITICAL POC
9.8 Jun 07

Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 2 and earlier, 6 Up

CVE-2015-4852 CRITICAL POC
9.8 Nov 18

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

CVE-2012-5076 CRITICAL POC
9.8 Oct 16

Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 7 and earlier allow

CVE-2017-3066 CRITICAL POC
9.8 Apr 27

Remote unauthenticated attackers can execute arbitrary code on Adobe ColdFusion servers through Java deserialization fla

CVE-2012-0391 CRITICAL POC
9.8 Jan 08

The ExceptionDelegator component in Apache Struts before 2.2.3.1 interprets parameter values as OGNL expressions during

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy