Answer in brief
CVE-2026-77597 records a Low severity (CVSS 3.5) vulnerability in iSponsorBlockTV: SSRF via Malicious SSDP Response Spoofing in Local Device Discovery. The current sources do not mark it as known exploited. The current feed maps dmunozv04/iSponsorBlockTV (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 3.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps dmunozv04/iSponsorBlockTV (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| dmunozv04/iSponsorBlockTVgeneric | <2.11.0 | 2.11.0 |
Published upstream
Nov 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 16, 2026
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.
Quoted source text, attributed separately from HOL analysis.