Vulnerability in @mariozechner/pi-coding-agent (CVE-2026-54327)
Summary
Vulnerability in @mariozechner/pi-coding-agent (CVE-2026-54327). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.78.1 or later.
Original description
The description as published by the source.
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.
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-54327 has been found in @mariozechner/pi-coding-agent.
Risk of unauthorized operations or information disclosure. CVSS score: 2.2/10.
What to do: upgrade @mariozechner/pi-coding-agent to 0.78.1 or later.
If unsure, ask your IT team or search "@mariozechner/pi-coding-agent CVE-2026-54327" on the vendor's site.
CVE-2026-54327 (@mariozechner/pi-coding-agent) — CWE-367 / CVSS v3 2.2
Attack vector: local
Patched: 0.78.1 — apply immediately
Workaround: If upgrading immediately is not possible, restrict the Pi agent configuration directory so only the owning user can traverse it, restrict auth.json to owner-only permissions, and run Pi with a restrictive umask such as 077 until the upgrade is co
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-367) exists in @mariozechner/pi-coding-agent.
Check the vendor advisory for the affected versions of @mariozechner/pi-coding-agent.
Severity: Low (CVSS 2.2/10). Risk of unauthorized operations or information disclosure.
Update to 0.78.1.
Workaround: If upgrading immediately is not possible, restrict the Pi agent configuration directory so only the owning user can traverse it, restrict auth.json to owner-only permissions, and run Pi with a restrictive umask such as 077 until the upgrade is co
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@mariozechner/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 '@mariozechner/pi-coding-agent' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@mariozechner/pi-coding-agentを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
If upgrading immediately is not possible, restrict the Pi agent configuration directory so only the owning user can traverse it, restrict `auth.json` to owner-only permissions, and run Pi with a restrictive umask such as `077` until the upgrade is coパッチが適用されるまでの応急処置として、If upgrading immediately is not possible, restrict the Pi agent configuration directory so only the owning user can traverse it, restrict
auth.jsonto owner-only permissions, and run Pi with a restrictive umask such as077until the upgrade is co を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade @mariozechner/pi-coding-agent to 0.78.1ステージング環境で 0.78.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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
- web github.com
- web github.com