CVE-2026-77597: dmunozv04 iSponsorBlockTV · Server-Side Request Forgery
Affects dmunozv04 iSponsorBlockTVSource CVE Database V5
Not known to be exploited · CVSS 3.5 Low : upgrade to 2.11.0 when convenient.
Data as of 16 Nov 2026, 21:05 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 3.5 |
|---|
- Patch
- Available – fixed in 2.11.0
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade dmunozv04 iSponsorBlockTV to 2.11.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| dmunozv04iSponsorBlockTV | Affected
| Fixed in
|
AI-suggested
Upgrade iSponsorBlockTV to version 2.11.0 or later, where the vulnerability is fixed. No additional mitigation actions are required as the fix addresses the root cause by validating the SSDP LOCATION URL destination.
Description
CVE-2026-77597 is a server-side request forgery (SSRF) vulnerability in iSponsorBlockTV versions prior to 2.11.0. The vulnerability arises because the application trusts the SSDP LOCATION URL from local network responders without validating the destination. This can lead to attacker-directed GET and constrained POST requests to internal services, but response data and errors are not returned to the attacker, resulting in blind SSRF with limited impact. The issue is fixed in version 2.11.0.