CVE-2026-54327
LOWCVE-2026-54327 is a low-severity (CVSS 2.2) CWE-367 vulnerability in @mariozechner/pi-coding-agent. O3 Security confirms whether CVE-2026-54327 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Pi: Race condition in auth.json writes could expose stored credentials
Blast Radius
@mariozechner/pi-coding-agent📦@earendil-works/pi-coding-agentReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @mariozechner/pi-coding-agent | ≥ 0.28.0 | No fix |
| 📦npm | @earendil-works/pi-coding-agent | ≥ 0.74.0&&< 0.78.1 | 0.78.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @mariozechner/pi-coding-agent. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
No patched version of @mariozechner/pi-coding-agent has shipped for CVE-2026-54327 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-54327 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2026-54327. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-54327 in your dependencies?
O3 detects CVE-2026-54327 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.