Pi is a minimal terminal coding harness. Pi before 0.79.0 loaded project-local configuration and resources from a repository's .pi directory without first asking the user to trust that repository. This included project-local extensions, which are executable TypeScript or JavaScript modules loaded into the Pi process. An attacker who controls a repository could place Pi-specific project resources in that repository. If a user then started Pi from that working tree, the project-local extension code could run with the same privileges as the local Pi process without the user having a convenient way to make a trust decision. This vulnerability is fixed in 0.79.0.
CVE-2026-54325
This medium-severity CVE scores 4.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 98% 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).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.4
- EG Score
- 4.4(medium)
- EPSS
- 2.0%
- KEV
- Not listed
Published
June 17, 2026
Last Modified
June 25, 2026
Advisory Details (7)
Auto-updated Jun 24, 2026Pi loads project-local extensions without approval · Advisory · earendil-works/pi · GitHub
Affected: 0.79.0 released.
https://github.com/earendil-works/pi/security/advisories/GHSA-mqxh-6gq7-558mv0.79.0
Patch available: earendil-works/pi v0.79.0
https://github.com/earendil-works/pi/releases/tag/v0.79.0commit ff3e9df5f5b3 (earendil-works/pi)
Fix landed in earendil-works/pi commit ff3e9df5f5b3 — awaiting tagged release
https://github.com/earendil-works/pi/commit/ff3e9df5f5b32368c20b0ef553a6834b3dee9350commit ce3a72444e1c (earendil-works/pi)
Fix landed in earendil-works/pi commit ce3a72444e1c — awaiting tagged release
https://github.com/earendil-works/pi/commit/ce3a72444e1cc1eaa50475fb3378c7ffbb53ef49commit 89a92207f1c9 (earendil-works/pi)
Fix landed in earendil-works/pi commit 89a92207f1c9 — awaiting tagged release
https://github.com/earendil-works/pi/commit/89a92207f1c9303d53d822fd9b0ac21578834cb4commit 718215bd95b6 (earendil-works/pi)
Fix landed in earendil-works/pi commit 718215bd95b6 — awaiting tagged release
https://github.com/earendil-works/pi/commit/718215bd95b6fc6fa251580d27ea8aab857de390commit 38f18be44727 (earendil-works/pi)
Fix landed in earendil-works/pi commit 38f18be44727 — awaiting tagged release
https://github.com/earendil-works/pi/commit/38f18be44727e669eb0a6e2eb8edb51b0232d83cVendor Advisories for CVE-2026-54325(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| @earendil-works/pi-coding-agent | — | 0.79.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 34× 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 21:57 UTCEG score recompute
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-05 22:06 UTCEG score recompute
- 2026-07-05 00:08 UTCEG score recompute
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 02:09 UTCEG score recompute
- 2026-07-03 04:04 UTCEG score recompute
- 2026-07-02 06:05 UTCEG score recompute
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 08:06 UTCEG score recompute
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 10:06 UTCEG score recompute
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 11:56 UTCEG score recompute
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 13:57 UTCEG score recompute
- 2026-06-27 16:00 UTCEG score recompute
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 18:00 UTCEG score recompute
- 2026-06-25 20:02 UTCEG score recompute
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-24 22:02 UTCEG score recompute
Show 9 moreShow fewer
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-24 00:04 UTCEG score recompute
- 2026-06-23 02:06 UTCEG score recompute
- 2026-06-22 04:07 UTCEG score recompute
- 2026-06-21 06:08 UTCEG score recompute
- 2026-06-20 08:07 UTCEG score recompute
- 2026-06-19 10:06 UTCEG score recompute
- 2026-06-18 12:08 UTCEG score recompute
- 2026-06-17 14:06 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-54325?
When was CVE-2026-54325 disclosed?
Is CVE-2026-54325 actively exploited?
What is the CVSS score of CVE-2026-54325?
How do I remediate CVE-2026-54325?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54325
Is Your Infrastructure Affected by CVE-2026-54325?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.