### 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
### 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
Update io.nextflow:nextflow to 25.10.6; io.nextflow:nextflow to 26.04.3 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scannextflow auth login command has incorrect default permissions affects io.nextflow:nextflow (maven), io.nextflow:nextflow (maven). Severity is medium. ### 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
AI coding agents often install or upgrade packages automatically in maven. A medium vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| io.nextflow:nextflowmaven | >=25.09.2-edge,<25.10.6 | 25.10.6 |
| io.nextflow:nextflowmaven | >=26.00.0-edge,<26.04.3 | 26.04.3 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL GuardUpdate io.nextflow:nextflow to 25.10.6; io.nextflow:nextflow to 26.04.3 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scannextflow auth login command has incorrect default permissions affects io.nextflow:nextflow (maven), io.nextflow:nextflow (maven). Severity is medium. ### 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
AI coding agents often install or upgrade packages automatically in maven. A medium vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| io.nextflow:nextflowmaven | >=25.09.2-edge,<25.10.6 | 25.10.6 |
| io.nextflow:nextflowmaven | >=26.00.0-edge,<26.04.3 | 26.04.3 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard