Local credential disclosure via permissive config rewrite
Published May 18, 2026 · Updated May 18, 2026
Insecure file permissions in Summarize before 0.15.1 allow local users to read API keys and provider credentials from its configuration. The refresh-free path writes a temporary replacement for ~/.summarize/config.json using process-umask permissions instead of preserving owner-only access. Exposure requires a shared Unix-like host, stored secrets, a permissive umask, and execution of summarize refresh-free; the consequence is credential disclosure.
Summary
What happened
Insecure file permissions in Summarize before 0.15.1 allow local users to read API keys and provider credentials from its configuration. The refresh-free path writes a temporary replacement for ~/.summarize/config.json using process-umask permissions instead of preserving owner-only access. Exposure requires a shared Unix-like host, stored secrets, a permissive umask, and execution of summarize refresh-free; the consequence is credential disclosure.
The record
- CVE
- CVE-2026-45246
- Published
- May 18, 2026
- Updated
- May 18, 2026
- Vendor
- Peter Steinberger
- Product
- Summarize
- Classifications
- CWE-732, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 18, 2026CVE publishedPublication date reported by the CVE source.
- May 18, 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.15.1
What conditions does exploitation require?
What is affected?
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
- Upstream safe reproduction for refresh-free permission wideningproof of concept · demonstrated
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