Local credential disclosure via permissive auth.json creation
Published Jun 23, 2026 · Updated Jun 23, 2026
Credential exposure in Pi 0.28.0 through 0.78.0 allows local users to read stored provider credentials during auth.json writes. FileAuthStorageBackend wrote auth.json using permissions inherited from the process umask, then changed its mode to 0600 in a separate operation. Exploitation requires access to the same machine, traversal of the victim's Pi configuration directory, and a successful read during the brief write interval.
Summary
What happened
Credential exposure in Pi 0.28.0 through 0.78.0 allows local users to read stored provider credentials during auth.json writes. FileAuthStorageBackend wrote auth.json using permissions inherited from the process umask, then changed its mode to 0600 in a separate operation. Exploitation requires access to the same machine, traversal of the victim's Pi configuration directory, and a successful read during the brief write interval.
The record
- CVE
- CVE-2026-54327
- Published
- Jun 23, 2026
- Updated
- Jun 23, 2026
- Vendor
- Earendil Inc.
- Product
- Pi
- Classifications
- CWE-367, CWE-732, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 23, 2026CVE publishedPublication date reported by the CVE source.
- Jun 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 0.74.0, < 0.78.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo