CVE-2026-77597: iSponsorBlockTV: SSRF via Malicious SSDP Response Spoofing in Local Device Discovery

Published Nov 16, 2026
·
Updated

iSponsorBlockTV is a SponsorBlock client for YouTube TV clients. Prior to 2.11.0, src/iSponsorBlockTV/dialclient.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.

Affected Software

1 affected component
iSponsorBlockTV<2.11.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.11.0

Event History

Nov 16, 2026
CVE Published
via MITRE·08:46 PM
Data Sourced
via MITRE·08:46 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who is exposed to this issue?

Deployments running iSponsorBlockTV before version 2.11.0 are affected when automatic local-device discovery is used. An attacker must be able to act as a responder on the local network and induce user interaction, as reflected by the adjacent-network and user-interaction attack vector.

2

What can an attacker do through the SSRF?

A malicious SSDP response can direct iSponsorBlockTV to make an attacker-selected destination GET request and a constrained POST request to a path ending in /YouTube. The POST headers and payload are application-defined, not attacker-controlled, and response data or errors are not returned to the attacker.

3

How can we remediate the issue?

Upgrade iSponsorBlockTV to version 2.11.0, which fixes the SSDP LOCATION URL validation issue.

4

How can we determine whether we are affected?

Check the deployed iSponsorBlockTV version and whether it is earlier than 2.11.0. Also determine whether automatic discovery is active and whether untrusted devices can respond to SSDP discovery on the local network.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203