Vulnerabilities in pkg:maven/io.nextflow/nextflow

PACKAGE
Advisory Identifier: GHSA-92qf-fcph-v5wr
Advisory Summary

CVE-2026-48722 is a MODERATE (CVSS 5.5) nextflow auth login command has vulnerability (CWE-732: Incorrect Permission Assignment for Critical Resource) affecting Nextflow libraries in the Maven ecosystem. The issue involves nextflow auth login command has incorrect default permissions. Remediation is available by upgrading affected packages to version 25.10.6, 26.04.3.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:maven/io.nextflow/nextflow

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:maven/io.nextflow/nextflow. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-92qf-fcph-v5wr CVE-2026-48722 MODERATE nextflow auth login command has incorrect default permissions

CVE-2026-48722 at a Glance

CVE Identifier CVE-2026-48722
GHSA Identifier GHSA-92qf-fcph-v5wr
Severity MODERATE
CVSS v3.1 Base Score 5.5
CWE Classification CWE-732: Incorrect Permission Assignment for Critical Resource
Affected Product Nextflow
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 5.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-48722

To remediate this vulnerability, upgrade all affected Nextflow dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

io.nextflow:nextflow fixed: 25.10.6
<dependency>
    <groupId>io.nextflow</groupId>
    <artifactId>nextflow</artifactId>
    <version>25.10.6</version>
</dependency>
io.nextflow:nextflow fixed: 26.04.3
<dependency>
    <groupId>io.nextflow</groupId>
    <artifactId>nextflow</artifactId>
    <version>26.04.3</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree -Dincludes=io.nextflow

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-48722, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=io.nextflow

Analyze the terminal output to locate any version of Nextflow in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 25.10.6), your application is affected.

Note: The mvn dependency:tree -Dincludes=io.nextflow command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-732: Incorrect Permission Assignment for Critical Resource, where the product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors. In Nextflow, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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

CVE-2026-48722 Affected Nextflow Versions

2 component(s)
Fixed Versions:
25.10.626.04.3
Product / Package Ecosystem Affected Versions Fixed Version
io.nextflow:nextflow
Maven
≥ 25.09.2-edge
< 25.10.6
25.10.6
io.nextflow:nextflow
Maven
≥ 26.00.0-edge
< 26.04.3
26.04.3

References

Frequently Asked Questions

What is CVE-2026-48722?
CVE-2026-48722 is a security vulnerability in Nextflow involving nextflow auth login command has incorrect default permissions under CWE-732: Incorrect Permission Assignment for Critical Resource.
Which Nextflow versions are affected?
Affected versions include releases prior to 25.10.6, 26.04.3 across affected packages: io.nextflow:nextflow.
What version fixes CVE-2026-48722?
Upgrading to 25.10.6, 26.04.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is nextflow affected?
Yes, io.nextflow:nextflow is affected in releases prior to 25.10.6, 26.04.3. Upgrade your dependency to 25.10.6, 26.04.3 or later.
What is the CVSS score of CVE-2026-48722?
CVE-2026-48722 has a CVSS v3.1 base score of 5.5 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2026-48722?
CVE-2026-48722 is classified under CWE-732: Incorrect Permission Assignment for Critical Resource (The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.).
How can I check Maven dependencies for CVE-2026-48722?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=io.nextflow'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-92qf-fcph-v5wr",
  "modified" : "2026-06-25T21:45:55Z",
  "published" : "2026-06-25T21:45:55Z",
  "aliases" : [ "CVE-2026-48722" ],
  "summary" : "nextflow auth login command has incorrect default permissions",
  "details" : "### Impact\n\n`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).\n\nOn 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.\n\nSingle-user systems and headless CI runners, which do not invoke the interactive login flow, are not affected.\n\nAffected versions:  `25.09.2-edge` through `26.04.1`.\n  \n### Patches\n\nFixed 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.\n\nTokens 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.\n\n### Workarounds\n  \nRestrict the file and its parent directory:\n\n`chmod 600 \"${NXF_HOME:-$HOME/.nextflow}/seqera-auth.config\"`\n`chmod 700 \"${NXF_HOME:-$HOME/.nextflow}\"`\n\nAlternatively, supply the Platform token via the `TOWER_ACCESS_TOKEN` environment variable instead of running `nextflow auth login`.\n\n### References\n  \n  - https://cwe.mitre.org/data/definitions/276.html",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "io.nextflow:nextflow"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "25.09.2-edge"
      }, {
        "fixed" : "25.10.6"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "io.nextflow:nextflow"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "26.00.0-edge"
      }, {
        "fixed" : "26.04.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/nextflow-io/nextflow/security/advisories/GHSA-92qf-fcph-v5wr"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/nextflow-io/nextflow"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-276", "CWE-732" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-25T21:45:55Z",
    "nvd_published_at" : null
  }
}