CVE-2026-54327

LOWPre-NVD 2.22.2—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 99% of all CVEs by exploit prediction. 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: epss, secondary
2.2EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: <0.1%CVSS: 2.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Pi is a minimal terminal coding harness. From 0.74.0 until 0.78.1, Pi stored API keys and OAuth credentials in auth.json. A race condition in the file write path could briefly create or rewrite this file with permissions derived from the process umask before tightening the file to owner-only permissions. This vulnerability is fixed in 0.78.1.

CVSS v3
2.2
EG Score
2.2LOWmedium confidence
EG Risk
14
EG Risk 14/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity22% × 45%
Exploitation0% × 40%
Automatability30% × 15%
EPSS PROB
<0.1%
EPSS %ILE
below the 1st
KEV
Not listed

Published

June 17, 2026

Last Modified

June 26, 2026

References (3)

Vendor Advisories for CVE-2026-54327(1)

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

Affected Packages

(2 across 1 ecosystem)
npm(2)
PackageVulnerable rangeFix by version rangeDependents
@earendil-works/pi-coding-agent—
  • 0.74.0 up to 0.78.1: fixed in 0.78.1
—
@mariozechner/pi-coding-agent—
  • 0.28.0 through 0.73.1: no fix on record
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 20× 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-10-07 23:48 UTCEPSS rescore
  2. 2026-10-06 15:18 UTCEPSS rescore
  3. 2026-10-04 23:22 UTCEPSS rescore
  4. 2026-10-03 14:26 UTCEPSS rescore
  5. 2026-10-03 06:09 UTCOSV refresh
  6. 2026-10-01 19:50 UTCEPSS rescore
  7. 2026-09-30 15:03 UTCEPSS rescore
  8. 2026-09-28 13:51 UTCEPSS rescore
  9. 2026-09-27 13:48 UTCEPSS rescore
  10. 2026-09-26 15:59 UTCEPSS rescore
  11. 2026-09-24 14:04 UTCEPSS rescore
  12. 2026-09-23 17:54 UTCEPSS rescore
  13. 2026-09-17 19:31 UTCEPSS rescore
  14. 2026-09-16 14:08 UTCEPSS rescore
  15. 2026-09-16 05:15 UTCEPSS rescore
  16. 2026-09-14 03:09 UTCEG score recompute
  17. 2026-09-13 16:47 UTCEPSS rescore
  18. 2026-09-11 14:53 UTCEPSS rescore
  19. 2026-09-10 09:35 UTCEPSS rescore
  20. 2026-09-08 22:01 UTCEPSS rescore
  21. 2026-09-07 16:01 UTCEPSS rescore
  22. 2026-09-06 13:47 UTCEPSS rescore
  23. 2026-09-04 05:06 UTCEPSS rescore
  24. 2026-09-01 13:54 UTCEPSS rescore
  25. 2026-08-30 22:26 UTCEG score recompute
Show 44 more
  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-28 21:41 UTCEPSS rescore
  3. 2026-08-27 14:25 UTCEPSS rescore
  4. 2026-08-26 14:46 UTCEPSS rescore
  5. 2026-08-23 04:30 UTCEG score recompute
  6. 2026-08-23 00:19 UTCEPSS rescore
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 08:12 UTCEG score recompute
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-16 02:14 UTCEPSS rescore
  11. 2026-08-11 13:15 UTCEG score recompute
  12. 2026-08-08 16:37 UTCEPSS rescore
  13. 2026-08-08 11:10 UTCEG score recompute
  14. 2026-08-06 13:47 UTCEPSS rescore
  15. 2026-08-05 19:17 UTCEPSS rescore
  16. 2026-08-02 05:48 UTCEG score recompute
  17. 2026-07-30 16:28 UTCEPSS rescore
  18. 2026-07-30 03:44 UTCEG score recompute
  19. 2026-07-28 15:37 UTCEPSS rescore
  20. 2026-07-26 19:12 UTCEG score recompute
  21. 2026-07-26 14:54 UTCEPSS rescore
  22. 2026-07-24 14:18 UTCEPSS rescore
  23. 2026-07-23 14:18 UTCEPSS rescore
  24. 2026-07-23 03:19 UTCEG score recompute
  25. 2026-07-22 14:08 UTCEPSS rescore
  26. 2026-07-21 15:25 UTCEPSS rescore
  27. 2026-07-18 10:04 UTCEPSS rescore
  28. 2026-07-16 17:03 UTCEPSS rescore
  29. 2026-07-13 22:31 UTCEPSS rescore
  30. 2026-07-09 19:10 UTCEPSS rescore
  31. 2026-07-09 19:10 UTCEPSS rescore
  32. 2026-07-08 15:16 UTCEPSS rescore
  33. 2026-07-08 15:16 UTCEPSS rescore
  34. 2026-07-07 13:46 UTCEPSS rescore
  35. 2026-07-07 13:46 UTCEPSS rescore
  36. 2026-07-06 02:23 UTCEPSS rescore
  37. 2026-07-06 02:23 UTCEPSS rescore
  38. 2026-07-01 15:07 UTCEPSS rescore
  39. 2026-06-29 14:06 UTCEPSS rescore
  40. 2026-06-29 14:06 UTCEPSS rescore
  41. 2026-06-28 04:56 UTCEPSS rescore
  42. 2026-06-28 04:56 UTCEPSS rescore
  43. 2026-06-24 14:05 UTCEPSS rescore
  44. 2026-06-17 14:06 UTCEG score recompute

Related CVEs(same product + same CWE)

Same product

3 shown

npm:@mariozechner/pi-coding-agent · npm:@earendil-works/pi-coding-agent

Frequently asked(5)

What is CVE-2026-54327?
CVE-2026-54327 is a low vulnerability published on June 17, 2026. Pi is a minimal terminal coding harness. From 0.74.0 until 0.78.1, Pi stored API keys and OAuth credentials in auth.json. A race condition in the file write path could briefly create or rewrite this file with permissions derived from the process umask before tightening the file to owner-only…
When was CVE-2026-54327 disclosed?
CVE-2026-54327 was first published on June 17, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54327 actively exploited?
CVE-2026-54327 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a <0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54327?
CVE-2026-54327 has a CVSS base score of 2.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54327?
A fix for CVE-2026-54327 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54327 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54327

Explore →

Is Your Infrastructure Affected by CVE-2026-54327?

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

Book a Demo →Browse All CVEs