Local credential disclosure via default config permissions
Published May 11, 2026 · Updated May 11, 2026
Incorrect permissions in Summarize 0.14.1 and earlier allow local users to read daemon bearer tokens and API credentials from daemon.json. The writeDaemonConfig function creates ~/.summarize and writes daemon.json without explicit private modes, so common Unix-like umasks can leave the credential file world-readable. Another local account on a shared Linux or macOS host can recover provider keys or use the stolen bearer token against a running loopback daemon.
Summary
What happened
Incorrect permissions in Summarize 0.14.1 and earlier allow local users to read daemon bearer tokens and API credentials from daemon.json. The writeDaemonConfig function creates ~/.summarize and writes daemon.json without explicit private modes, so common Unix-like umasks can leave the credential file world-readable. Another local account on a shared Linux or macOS host can recover provider keys or use the stolen bearer token against a running loopback daemon.
The record
- CVE
- CVE-2026-45222
- Published
- May 11, 2026
- Updated
- May 11, 2026
- Vendor
- steipete
- Product
- Summarize
- Classifications
- CWE-732, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 11, 2026CVE publishedPublication date reported by the CVE source.
- May 11, 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 <=0.14.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