# CVE-2026-48722: Nextflow: Incorrect default permissions in the nextflow auth login command

> Local attackers can read Nextflow auth tokens due to insecure file permissions, enabling impersonation of the victim on Seqera Platform.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-92qf-fcph-v5wr

## What is CVE-2026-48722?

CVE-2026-48722 is a medium-severity vulnerability in nextflow-io nextflow, published on 15 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource), CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2026-48722?

4 open source packages ship an affected version, including io.nextflow:nextflow.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.nextflow:nextflow` | Maven | From 25.09.2-edge | 25.10.6 |
| `io.nextflow:nextflow` | Maven | From 25.09.2-edge | 25.10.6 |
| `io.nextflow:nextflow` | Maven | From 26.00.0-edge | 26.04.3 |
| `io.nextflow:nextflow` | Maven | From 26.00.0-edge | 26.04.3 |

## How do I fix CVE-2026-48722?

Upgrade io.nextflow:nextflow to a fixed version for your release line: 25.10.6 or 26.04.3.

## Is CVE-2026-48722 being exploited?

There is no known exploitation of CVE-2026-48722 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48722 and fix it if it is affected.

What it is: CVE-2026-48722 is a medium-severity vulnerability in nextflow-io nextflow, published on 15 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-48722 in the wild and no public exploit code.

Affected packages and fixed versions:
- io.nextflow:nextflow (Maven): affected from 25.09.2-edge; fixed in 25.10.6
- io.nextflow:nextflow (Maven): affected from 25.09.2-edge; fixed in 25.10.6
- io.nextflow:nextflow (Maven): affected from 26.00.0-edge; fixed in 26.04.3
- io.nextflow:nextflow (Maven): affected from 26.00.0-edge; fixed in 26.04.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48722/ (Markdown: https://insights.sbomify.com/CVE-2026-48722/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48722
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48722
- OSV: https://osv.dev/vulnerability/CVE-2026-48722

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48722/
Summaries are generated and may contain mistakes; the official description above is the record.