cve.bz

CVE-2026-48722 nextflow-io nextflow: Incorrect Default Permissions

5.5 mediumEPSS 0.1%Fix available

Medium (5.5) in nextflow-io nextflow. EPSS 0.1% estimated probability of exploitation activity in the next 30 days. Fixed in io.nextflow:nextflow 25.10.6, 26.04.3.

On this page
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.

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 4th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-09-17. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-276 Incorrect Default Permissions
CWE-732 Incorrect Permission Assignment for Critical Resource
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • io.nextflow:nextflow (Maven): fixed in 25.10.6, 26.04.3

Ask an AI about this CVE

Show the promptExplain CVE-2026-48722 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-48722?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-48722?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-48722 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
nextflow-io nextflow>= 25.09.2-edge, < 25.10.6
nextflow-io nextflow>= 25.11.0-edge, < 26.04.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-92qf-fcph-v5wrMavenio.nextflow:nextflow>=25.09.2-edge <25.10.625.10.6
GHSA-92qf-fcph-v5wrMavenio.nextflow:nextflow>=26.00.0-edge <26.04.326.04.3

Attack patterns (CAPEC)

  • CAPEC-1 Accessing Functionality Not Properly Constrained by ACLs Likelihood: High · Severity: High
  • CAPEC-81 Web Server Logs Tampering Likelihood: Medium · Severity: High
  • CAPEC-127 Directory Indexing Likelihood: High · Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-732 (11).

References

Check your stackJSON