Cyber Resilience

CVE-2026-45245

SSRF in Steipete Summarize ≤ 0.15.1

Public PoCSSRF
Published
18 May 2026
Modified
14 July 2026
Patch / advisory
CVSS Score v4 4.6
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:L/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0033 26th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-45245 is a medium-severity SSRF (CWE-918) vulnerability in Steipete Summarize. Its CVSS base score is 4.6 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique ARP Cache Poisoning (T1557.002); ranked at the 26th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to AC-17 (Remote Access) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Summarize prior to 0.15.1 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…

more

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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1557.002 ARP Cache Poisoning Credential Access
Adversaries may poison Address Resolution Protocol (ARP) caches to position themselves between the communication of two or more networked devices.
T1557 Adversary-in-the-Middle Credential Access
Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as [Network Sniffing](https://attack.
T1557.001 Name Resolution Poisoning and SMB Relay Credential Access
By responding to LLMNR/NBT-NS/mDNS network traffic, adversaries may spoof an authoritative source for name resolution to force communication with an adversary controlled system.
T1557.003 DHCP Spoofing Credential Access
Adversaries may redirect network traffic to adversary-owned systems by spoofing Dynamic Host Configuration Protocol (DHCP) traffic and acting as a malicious DHCP server on the victim network.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-45244Same product: Steipete Summarize
CVE-2026-45243Same product: Steipete Summarize
CVE-2026-45242Same product: Steipete Summarize
CVE-2026-45246Same product: Steipete Summarize
CVE-2023-7004Shared CWE-940
CVE-2026-22269Shared CWE-940
CVE-2024-40515Shared CWE-940
CVE-2024-40516Shared CWE-940
CVE-2024-37663Shared CWE-940
CVE-2024-1621Shared CWE-940

Affected Assets

steipete
summarize
≤ 0.15.1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.3.6
  • V1.5.3
  • V5.3.2
  • V10.4.7

Mitigating Controls (NIST 800-53 r5) AI

IA-3 requires unique identification and authentication of devices before any communication channel is established, directly stopping acceptance of unverified origins.

AC-17 mandates documented restrictions and authentication requirements for remote access, blocking channels whose origins are not properly verified.

Information flow enforcement can restrict which destinations the server is allowed to contact on behalf of users.

Input validation directly stops untrusted URLs from being accepted and fetched without destination checks.

SC-23 protects session authenticity, ensuring the source of an established communication channel is verified and cannot be spoofed.

Boundary protection limits the network reach of server-initiated requests even if SSRF occurs.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-03 full match
prevents

Authentication of users/services/hardware directly enforces source verification for communication channels.

PR.AA-04 mostly match
prevents

Verifying identity assertions prevents spoofed channel origins but does not cover all channel-establishment scenarios.

PR.PS-06 mostly match
prevents

Secure development practices directly include input validation and destination allow-listing that prevent SSRF.

DE.CM-09 partial match
prevents

Runtime monitoring of web applications and services can detect anomalous outbound requests indicative of SSRF.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover and record SSRF flaws in web applications.

PR.IR-01 partial match
prevents

Network segmentation and egress controls can limit the damage from successful SSRF requests.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Secure authentication mechanisms verify the identity and origin of communication channel initiators.

prevents

Operational threat data describing SSRF campaigns can be used to tighten outbound-request allow-lists and detection rules before attackers exploit them.

degrades

Network security controls enforce source verification and channel authentication for incoming communications.

degrades

Security of network services includes validating the origin of service requests and connections.

mitigates

Network segregation limits exposure but does not directly verify source of individual channels.

prevents

Cryptography can support channel authentication but does not inherently verify source without proper implementation.

References