CVE-2026-53782: steipete Summarize SSRF in podcast RSS transcript fetching

CVE-2026-53782 · Severity: high · CVSS 7.4 · Published 2026-06-11

@steipete/summarize is a popular tool for generating summaries from URLs, podcasts, and files. The application can fetch podcast transcript URLs from RSS feeds controlled by attackers. A vulnerability allows an attacker who controls an RSS feed to direct the application to fetch transcript content from internal network addresses (loopback, private IP ranges, link-local addresses) or redirect such requests, potentially exposing sensitive internal service responses.

Technologies: @steipete/summarize (npm), Steipete Summarize. Vendors: npm, Steipete.

Quick answers

Is CVE-2026-53782 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-53782 being exploited in the wild.
How severe is CVE-2026-53782?
High severity, with a CVSS score of 7.4, published 11 June 2026.
Which products and versions are affected?
@steipete/summarize (npm) < 0.17.0, SEMVER:introduced=0,fixed=0.17.0; Steipete Summarize < 0.17.0, before 0.17.0.
Is there a fix for CVE-2026-53782?
Yes. @steipete/summarize (npm): upgrade to 0.17.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-53782 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-53782?
Check whether you run @steipete/summarize (npm) or Steipete Summarize at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • @steipete/summarize (npm): upgrade to 0.17.0 or later
    npm install @steipete/summarize@0.17.0

Technical details

The vulnerability exists in the RSS podcast transcript provider (packages/core/src/content/transcript/providers/podcast/rss-transcript.ts) where feed-controlled `<podcast:transcript url="...">` values are passed directly to fetch without validation. The root cause is insufficient URL validation: transcript URLs were not checked for local/private address ranges, redirect targets were delegated to automatic fetch behavior without revalidation, and hostname resolution was not performed before request dispatch. An attacker who publishes or controls a podcast RSS feed can include transcript entries pointing to loopback (127.0.0.1), RFC 1918 private ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), link-local addresses (169.254.0.0/16), or URLs that redirect to such targets. When the application processes the feed, it will fetch from these internal services and potentially expose their responses. The fix validates transcript URL schemes (http/https only), blocks localhost and local/private IP destinations before fetch, resolves DNS answers and rejects private/local DNS responses, revalidates all redirect targets, and uses DNS-pinned fetch to prevent DNS rebinding. Fixed in version 0.17.0.

Affected products

  • steipete @steipete/summarize before 0.17.0

Identifiers

  • CVE-2026-53782
  • GHSA-3vx2-vqx8-jxfg

Timeline

  • 2026-06-11: disclosed: Vulnerability published in GHSA-3vx2-vqx8-jxfg
  • 2026-06-11: patched: Fixed in v0.17.0 release with security patch PR #239

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.