/

CVE-2026-85608

Severity:

HIGH RISK

(7.5)

SSRF (CWE-918) in Douyin TikTok Download API Endpoints

CVE-2026-85608

Deferred

Vulnerability type

Category:

Server-Side Request Forgery

CWE:

CWE-918

Impact:

Unauthorized Internal Service Access and Sensitive Data Exposure

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Douyin_TikTok_Download_API contains a server-side request forgery vulnerability in its download and video-data endpoints. An unauthenticated attacker may supply a URL that causes the server to request internal services or external destinations, potentially exposing response data such as cloud credentials through error messages.

Affected context

The vulnerability occurs in deployments where the /api/download or /api/hybrid/video_data endpoints accept a user-controlled url query parameter and use it to make outbound server-side requests. Risk is increased when the application can reach internal network services, cloud metadata endpoints, or returns upstream response content and errors to unauthenticated clients.

Exploit preconditions

  • Attack surface: The /api/download and /api/hybrid/video_data HTTP endpoints
  • Required access: No authentication may be required when the affected endpoints are exposed
  • Trigger point: Processing of a user-supplied url query parameter
  • Why exploitation is possible: The server makes outbound requests based on attacker-controlled destinations and may disclose returned content or error details

Why this happens

The underlying bug is insufficient control over a user-provided URL before the application uses it for server-side network access. This behavior maps to CWE-918: Server-Side Request Forgery, in which an attacker can influence a server into sending requests to unintended destinations. Without destination validation, network restrictions, and careful response handling, the server may become a proxy to internal services or sensitive metadata interfaces.

Potential impact

  • An attacker may access internal HTTP services that are not publicly reachable
  • Cloud instance metadata or temporary credentials could be exposed
  • Sensitive response bodies or diagnostic error messages could be disclosed
  • Internal services may receive unauthorized requests from a trusted network location
  • Network reconnaissance and follow-on compromise could become easier

General mitigation guidance

Mitigation generally focuses on reducing trust in user-supplied URLs and limiting the server's network reach.

Common defensive patterns include:

  • Allowing requests only to an explicit, narrowly defined destination allowlist
  • Validating schemes, hostnames, ports, redirects, and resolved addresses
  • Blocking loopback, link-local, private, and other non-public address ranges
  • Rechecking destinations after DNS resolution and across redirects
  • Restricting outbound network access with egress controls and cloud metadata protections
  • Returning minimal, sanitized errors without upstream response bodies or credentials
  • Applying authentication, authorization, rate limits, and least privilege to download functionality

How teams detect issues like this

Organizations commonly detect SSRF risks through:

  • Static analysis rules identifying HTTP clients that consume request parameters as URLs
  • Code review checks for missing destination allowlists, private-address filtering, and redirect validation
  • Dynamic testing with controlled external endpoints and blocked internal-address test cases
  • Network monitoring for application requests to loopback, private, link-local, and metadata addresses
  • Policy enforcement that restricts outbound traffic and prevents sensitive response content from reaching clients

Automated security review tools can help identify URL-fetching code paths, but findings should be verified against deployment network controls.

Sources

SourceLink
github.comgithub.com/Evil0ctal/Douyin_TikTok_Download_API
github.comgithub.com/Evil0ctal/Douyin_TikTok_Download_API/blob/V4.1.2/crawlers/douyin/web/utils.py
github.comgithub.com/Evil0ctal/Douyin_TikTok_Download_API/issues/729
vulncheck.comvulncheck.com/advisories/douyin-tiktok-download-api-4.1.2-ssrf-via-url-parameter

Frequently asked

questions

Yes, when the affected endpoints are publicly reachable and accept unauthenticated requests. Exploitation depends on the server being able to reach a useful internal or external destination.

The described issue does not require prior authentication. An attacker needs network access to an exposed endpoint and the ability to provide a URL parameter.

Avoid arbitrary server-side URL fetching where possible. Otherwise, use a strict destination allowlist, validate resolved addresses and redirects, enforce egress restrictions, and avoid returning upstream response details.

Treat all client-provided URLs as untrusted, combine application-layer validation with network-layer controls, protect cloud metadata services, and test URL-fetching features for internal and redirect-based access paths.

Find out what's already
exploitable in your codebase.