SSRF (Server-Side Request Forgery) in @steipete/summarize (CVE-2026-45245)
Summary
SSRF in @steipete/summarize (CVE-2026-45245). Confidential information can be exposed externally. Mitigation: upgrade to 0.15.1 or later.
Original description
The description as published by the source.
Summarize prior to 0.15.0 contains a vulnerability in the hover summary feature that allows malicious pages to dispatch synthetic mouseover events over attacker-controlled links, causing the extension to make authenticated daemon requests using stored tokens without verifying event trustworthiness. Attackers can place local or private-network URLs behind hoverable links to route authenticated requests through the daemon, potentially accessing sensitive internal endpoints when users interact with attacker-controlled content.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-45245 has been found in @steipete/summarize.
Confidential information can be exposed externally. CVSS score: 7.4/10.
What to do: upgrade @steipete/summarize to 0.15.1 or later.
If unsure, ask your IT team or search "@steipete/summarize CVE-2026-45245" on the vendor's site.
CVE-2026-45245 (@steipete/summarize) — CWE-918 / CVSS v3 7.4
Attack vector: remote (network-reachable) / unauthenticated
Patched: 0.15.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SSRF (CWE-918) exists in @steipete/summarize.
Check the vendor advisory for the affected versions of @steipete/summarize.
Severity: High (CVSS 7.4/10). Confidential information can be exposed externally.
Update to 0.15.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@steipete/summarize' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@steipete/summarize' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@steipete/summarizeを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @steipete/summarize to 0.15.1ステージング環境で 0.15.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory disclosure@vulncheck.com
- exploit github.com
- package github.com
- patch disclosure@vulncheck.com
- web disclosure@vulncheck.com
- web github.com
- web github.com