Summarize's hover summary feature allows malicious pages to dispatch synthetic mouseover events over attacker-controlled links
CVE-2026-45245GHSA-2r69-qgv3-hr65
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (@steipete/summarize 0.15.1), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
- Affected
- < 0.15.1
- Fixed in
- 0.15.1
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-2r69-qgv3-hr65 lists affected ranges: npm @steipete/summarize >=0 <0.15.1 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-2r69-qgv3-hr65 lists affected ranges: npm @steipete/summarize >=0 <0.15.1
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 4.6 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:L/VI:N/VA:N/SC:H/SI:N/SA:N · score source
- EPSS
- CVE-2026-45245: 0.33% estimated exploitation activity in the next 30 days; percentile 26.19 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
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.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-2r69-qgv3-hr65
- Revision 2 · amended ·
Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.
- Revision 1 · created ·
Published from osv record GHSA-2r69-qgv3-hr65
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-45245 Advisory: Summarize's hover summary feature allows malicious pages to dispatch synthetic mouseover events over attacker-controlled links IDs: CVE-2026-45245, GHSA-2r69-qgv3-hr65 Record: https://patchnext.com/advisories/cve-2026-45245 (revision 3, source checked 26 Oct 2026, 12:52 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 4.6) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: @steipete/summarize 0.15.1. A vendor fix does not mean a deployment is fixed. ## Affected components - npm @steipete/summarize: affected < 0.15.1; fixed in 0.15.1 ## Suggested inspection (read-only) - `npm ls @steipete/summarize --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on @steipete/summarize. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-2r69-qgv3-hr65 (OSV record GHSA-2r69-qgv3-hr65 lists affected ranges: npm @steipete/summarize >=0 <0.15.1 (fixed)) - Verified: https://github.com/advisories/GHSA-2r69-qgv3-hr65 (GitHub-reviewed advisory GHSA-2r69-qgv3-hr65 lists affected ranges: npm @steipete/summarize >=0 <0.15.1) Commands are suggestions: review each one before running it.
Loading voting…