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.
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 100% 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.2
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 2.2Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 2.2
- EG Score
- 2.2(medium)
- EPSS
- 0.1%
- KEV
- Not listed
Published
June 17, 2026
Last Modified
June 26, 2026
References (3)
- security-advisories@githubhttps://github.com/earendil-works/pi/commit/135fb545f99106a4a249274f129b90bc0a77d347
- security-advisories@githubhttps://github.com/earendil-works/pi/releases/tag/v0.78.1
- security-advisories@githubhttps://github.com/earendil-works/pi/security/advisories/GHSA-r95r-rj6r-c39x
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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| @earendil-works/pi-coding-agent | — | 0.78.1 | — |
| @mariozechner/pi-coding-agent | — | — | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 15× 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.
- 2026-07-06 02:41 UTCEG score recompute
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-03 00:35 UTCEG score recompute
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-06-29 22:30 UTCEG score recompute
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-26 20:25 UTCEG score recompute
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-23 18:20 UTCEG score recompute
- 2026-06-20 16:14 UTCEG score recompute
- 2026-06-17 14:06 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-732
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 in the National Vulnerability Database 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% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54327?
CVE-2026-54327 has a CVSS v3 base score of 2.2 (NVD).
How do I remediate CVE-2026-54327?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54327, 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
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54327
Is Your Infrastructure Affected by CVE-2026-54327?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.