CVE
iSponsorBlockTV server-side request forgery in device discovery
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
- Exploited
- No known exploitation
- Fix
- Fixed in 2.11.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.11.0.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 4/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
iSponsorBlockTV trusts a device address supplied during automatic local-network discovery without checking it. An attacker on the same local network can make the app send requests to internal services, with limited ability to change data, but cannot see the replies, and a user must take an action for this to happen.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Original description
iSponsorBlockTV is a SponsorBlock client for YouTube TV clients. Prior to 2.11.0, src/iSponsorBlockTV/dial_client.py trusts the SSDP LOCATION URL supplied by a local-network responder without validating its destination. During automatic discovery, this can cause an attacker-directed GET request and a constrained POST request to a path ending in /YouTube; the POST uses application-defined headers and an application-defined payload rather than attacker-selected request contents. The requests can reach internal services, but the detailed request behavior states that response data and errors are not returned to the attacker, making the demonstrated behavior blind SSRF with bounded integrity impact. This issue is fixed in version 2.11.0.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity3.5/10CVSS 3.5
- No patch0/5No signal
What would change the score
- Would score about 59 if added to CISA KEV
- Would score about 54 if CISA's SSVC rates exploitation active
- Would score about 26 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2.11.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-77597 (iSponsorBlockTV: SSRF via Malicious SSDP Response Spoofing in Local Device Discovery), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-77597 (entry last updated 2026-11-16):
Affected:
- dmunozv04 iSponsorBlockTV: fixed in 2.11.0
Fixed versions: 2.11.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-77597 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-77597 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/dmunozv04/iSponsorBlockTV/security/advisories/GHSA-56v3-jrq2-4q9m
- https://github.com/dmunozv04/iSponsorBlockTV/commit/7d315115f41523632588fb0b22d46d85807172b7
- https://github.com/dmunozv04/iSponsorBlockTV/releases/tag/v2.11.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-77597
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-77597"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- dmunozv04 iSponsorBlockTV
fixed in 2.11.0
Evidence 5
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 2
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-77597
Is CVE-2026-77597 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-77597?
iSponsorBlockTV: before 2.11.0.Source: cve.now feed data
How do I fix CVE-2026-77597?
Upgrade to a fixed version: 2.11.0.Source: cve.now feed data