{"answers":{"affected":"2 open source packages ship an affected version, including @steipete/summarize.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45222 exists.","fix":"Upgrade @steipete/summarize to 0.15.0 or later.","what":"CVE-2026-45222 is a medium-severity vulnerability in steipete summarize, published on 11 May 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-45222 and fix it if it is affected.\n\nWhat it is: CVE-2026-45222 is a medium-severity vulnerability in steipete summarize, published on 11 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45222 exists.\n\nAffected packages and fixed versions:\n- @steipete/summarize (npm): affected all versions; fixed in 0.15.0\n- @steipete/summarize (npm): affected all versions; fixed in 0.15.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-45222/ (Markdown: https://insights.sbomify.com/CVE-2026-45222/index.md)","id":"CVE-2026-45222","markdown":"https://insights.sbomify.com/CVE-2026-45222/index.md","name":"CVE-2026-45222","record":{"aliases":["GHSA-qp7v-gjgg-4mj6"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read","account_takeover"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Summarize npm package","requires_auth":"low_privilege","summary":"Local attackers can read world-readable daemon configuration files to steal bearer tokens and API credentials, leading to unauthorized access.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"Summarize versions through 0.14.1, fixed in commit 0cfb0fb, creates the daemon configuration directory and file with default filesystem permissions that may be world-readable on Unix-like systems, allowing local attackers to read bearer tokens and API credentials stored in ~/.summarize/daemon.json. A local attacker can exploit these permissive permissions to read the daemon bearer token and persisted provider credentials, enabling unauthorized access to the daemon or recovery of sensitive API keys.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Summarize Insecure Daemon Configuration File Permissions","id":"CVE-2026-45222","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Crabbox \u003c 0.9.0 Authentication Bypass via Admin Claim Injection","id":"CVE-2026-45223"},"packages":[{"ecosystem":"npm","fixed":["0.15.0"],"introduced":["0"],"last_affected":[],"package":"@steipete/summarize","purl":null,"source":"GHSA-qp7v-gjgg-4mj6"},{"ecosystem":"npm","fixed":["0.15.0"],"introduced":["0"],"last_affected":[],"package":"@steipete/summarize","purl":"pkg:npm/%40steipete/summarize","source":"GHSA-qp7v-gjgg-4mj6"}],"prev":{"headline":"Konga \u003c 2.1.0 Privilege Escalation via Hardcoded OpenSSL Path","id":"CVE-2026-45221"},"products":["summarize"],"published":"2026-05-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-08","vendors":["steipete"]},"summary":"Local attackers can read world-readable daemon configuration files to steal bearer tokens and API credentials, leading to unauthorized access.","url":"https://insights.sbomify.com/CVE-2026-45222/"}