Security readout for executives and security teams
Plain-English summary
Summarize before 0.15.1 could rewrite its configuration file with weaker filesystem permissions. On shared Unix-like systems, another local user may be able to read API keys or provider credentials stored in that file.
Executive priority
Treat this as a credential exposure risk, not a remote takeover. Prioritize shared developer, CI, or operations hosts where local users may access each other’s files, then rotate any potentially exposed credentials.
Technical view
The refresh-free configuration rewrite path creates a replacement config using default process umask permissions instead of preserving restrictive original permissions. This is CWE-732 and requires local user access, with high confidentiality impact and no stated integrity or availability impact.
Likely exposure
Exposure is most relevant on shared Unix-like hosts where untrusted or lower-privileged local users coexist with Summarize users. Single-user systems have lower practical risk, but credential exposure remains possible if backups or shared directories preserve weak permissions.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation evidence. Exploitation requires local user access and depends on the vulnerable refresh-free rewrite behavior producing a config file readable by other local users.
Researcher notes
Evidence supports a local information disclosure caused by insecure replacement-file permissions. The bundle identifies the patch commit and PR, but does not include exploit-in-the-wild claims. Validate behavior only in authorized environments and avoid publishing reproduction details that expose credentials.
Mitigation direction
- Upgrade Summarize to 0.15.1 or later; review v0.15.2 release notes for current vendor guidance.
- Restrict configuration file permissions on shared Unix-like systems so only the owning user can read credentials.
- Rotate API keys and provider credentials if the config was readable by other local users.
- Avoid running vulnerable versions on shared hosts until vendor guidance is applied.
Validation and detection
- Inventory Summarize installations and flag versions earlier than 0.15.1.
- Check whether affected systems are shared Unix-like hosts with multiple local users.
- Review configuration file permissions after refresh-free configuration rewrites.
- Confirm whether API keys or provider credentials were present in any exposed config file.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-732: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-45246 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.8 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N——VulnCheckCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N1.83.6VulnCheckVulnerability scoring details
Base CVSS 4.0 score
6.8MediumVector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/steipete/summarize/releases/tag/v0.15.2CVE reference, VulnCheck · release-notes
- https://github.com/steipete/summarize/pull/217CVE reference, VulnCheck · issue-tracking
- https://github.com/steipete/summarize/commit/9e990193650a23dab73f37d5e1964d574a44098bCVE reference, VulnCheck · patch
- https://www.vulncheck.com/advisories/summarize-insecure-file-permissions-information-disclosureCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Permission Assignment for Critical Resource
Incorrect Permission Assignment for Critical Resource represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.