Summarize EUVD-2026-30799

Exploitation requires: (1) the attacker holds a local user account on the same Unix-like system as the Summarize user (CVSS PR:L confirms authenticated local access is required); (2) the victim has run Summarize and the refresh-free configuration rewrite path has been exercised at least once, creating or overwriting the config file with default umask permissions; (3) the resulting config file is world-readable (i.e., the process umask was 022 or less restrictive, producing mode 0644 or wider). Exploitation is limited by: single-user or isolated-container deployments where no other local users exist (the most common developer workstation case); a restrictive umask (077) set before Summarize runs; or manual chmod hardening of the config file post-creation. The vulnerability does NOT affect confidentiality or integrity of data in transit, remote systems, or any path other than the refresh-free config rewrite code path.

CVSS 5.5 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) correctly frames this as a local, low-complexity, low-privilege issue with high confidentiality impact but no integrity or availability effect. The local attack vector (AV:L) and required low privileges (PR:L) are the primary risk limiters: exploitation requires an attacker who already has a shell session on the same machine. This materially constrains risk outside shared server or CI/CD pipeline environments. No EPSS data was provided in the input; no KEV listing exists; and no public exploit or proof-of-concept has been identified at time of analysis. The practical severity is higher than CVSS suggests on shared build servers or cloud development environments where multiple users share a host running Summarize - in those scenarios, credential theft is a realistic lateral-movement primitive. On single-user workstations the risk is negligible. There is no conflicting signal between the CVSS vector and the description: both consistently indicate local access is required.

An attacker with a local shell account on a shared Linux server (a CI/CD runner, a developer workstation with multiple users, or a cloud VM) runs 'cat ~/.config/summarize/config' (or equivalent path) after Summarize has been used by another user whose config was rewritten via the refresh-free path, reading the world-readable file directly to obtain API keys and provider credentials. No special tooling is required - standard filesystem read access is sufficient given the overly permissive file mode. The attacker can then use the extracted credentials to impersonate the victim against external AI providers or services integrated with Summarize. No public exploit code exists; the attack requires only knowledge of the config file location and a local user account.