CVE-2026-48722

MEDIUMPre-NVD 5.55.5
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 5.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:github_m
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: —CVSS: 5.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

nextflow auth login command has incorrect default permissions

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 `. 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

CVSS v3
5.5
EG Score
5.5(low)
EPSS
—
KEV
Not listed

Published

June 25, 2026

Last Modified

June 25, 2026

Vendor Advisories for CVE-2026-48722(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 8× in last 7d / 13× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 09:14 UTCEG score recompute
  2. 2026-07-06 10:17 UTCEG score recompute
  3. 2026-07-05 11:18 UTCEG score recompute
  4. 2026-07-04 12:21 UTCEG score recompute
  5. 2026-07-03 13:24 UTCEG score recompute
  6. 2026-07-02 14:27 UTCEG score recompute
  7. 2026-07-01 15:29 UTCEG score recompute
  8. 2026-06-30 16:32 UTCEG score recompute
  9. 2026-06-29 17:35 UTCEG score recompute
  10. 2026-06-28 18:37 UTCEG score recompute
  11. 2026-06-27 19:40 UTCEG score recompute
  12. 2026-06-26 20:42 UTCEG score recompute
  13. 2026-06-25 21:46 UTCEG score recompute

Frequently asked(4)

What is CVE-2026-48722?
CVE-2026-48722 is a medium vulnerability published on June 25, 2026. nextflow auth login command has incorrect default permissions 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…
When was CVE-2026-48722 disclosed?
CVE-2026-48722 was first published in the National Vulnerability Database on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-48722?
CVE-2026-48722 has a CVSS v4.0 base score of 5.5 (CNA self-assessment; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-48722?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48722, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-48722

Explore →

Is Your Infrastructure Affected by CVE-2026-48722?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs