Vulnerability in @earendil-works/pi-coding-agent (CVE-2026-54325)
Summary
Vulnerability in @earendil-works/pi-coding-agent (CVE-2026-54325). Risk of unauthorized operations or information disclosure. Exploitable via project_trust. Mitigation: upgrade to 0.79.0 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54325 has been found in @earendil-works/pi-coding-agent.
Attackers can target a specific entry point like project_trust over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.4/10.
What to do: upgrade @earendil-works/pi-coding-agent to 0.79.0 or later.
If unsure, ask your IT team or search "@earendil-works/pi-coding-agent CVE-2026-54325" on the vendor's site.
CVE-2026-54325 (@earendil-works/pi-coding-agent) — CWE-829 / CVSS v3 4.4
Attack vector: local / unauthenticated
Attack surface: project_trust
Patched: 0.79.0 — apply immediately
Workaround: and your workflow already enforces this trust boundary, continue to avoid running Pi directly in untrusted repositories.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-829) exists in @earendil-works/pi-coding-agent. Attackers reach the vulnerable code path via project_trust without authentication.
Check the vendor advisory for the affected versions of @earendil-works/pi-coding-agent. Attack surface: project_trust.
Severity: Medium (CVSS 4.4/10). Risk of unauthorized operations or information disclosure.
Update to 0.79.0.
Workaround: and your workflow already enforces this trust boundary, continue to avoid running Pi directly in untrusted repositories.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@earendil-works/pi-coding-agent' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@earendil-works/pi-coding-agent' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@earendil-works/pi-coding-agentを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
and your workflow already enforces this trust boundary, continue to avoid running Pi directly in untrusted repositories.パッチが適用されるまでの応急処置として、and your workflow already enforces this trust boundary, continue to avoid running Pi directly in untrusted repositories. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade @earendil-works/pi-coding-agent to 0.79.0ステージング環境で 0.79.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- patch github.com
- patch github.com
- patch github.com
- web github.com
- web github.com