Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-85608 – SSRF – Douyin_TikTok_Download_API ≤ 4.1.2

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-85608 is a Server-Side Request Forgery (SSRF) vulnerability in Evil0ctal’s Douyin_TikTok_Download_API, an open-source FastAPI/PyWebIO-based service that provides watermark-free downloading and parsing of Douyin/TikTok content. The flaw lets an unauthenticated attacker supply an arbitrary url query parameter that the server fetches on the attacker’s behalf, potentially exposing internal services, cloud metadata endpoints, and sensitive response data. The issue is rated HIGH severity (CVSS 8.7) and is remotely exploitable with no authentication or user interaction required.

Technical details

  • Root cause: The url query parameter accepted by the affected endpoints is not validated or restricted (no allowlist/denylist of destination hosts) before the server issues an outbound HTTP request to it.
  • Trigger conditions: An attacker sends a request to a vulnerable endpoint with a crafted url parameter pointing at an internal address or cloud metadata service; no prior authentication is needed.
  • Attack vector: Network — a single unauthenticated HTTP request to /api/download or /api/hybrid/video_data.
  • Impact: The server-side fetch can be used to reach internal-only services (e.g., cloud instance metadata endpoints), and responses/error messages returned to the attacker may leak credentials or other sensitive internal data. Confidentiality impact is high; integrity and availability are not affected.

Affected software

  • Douyin_TikTok_Download_API (Evil0ctal) — all versions through 4.1.2
  • Vulnerable endpoints: /api/download and /api/hybrid/video_data

Severity

  • CVSS v3.1: 7.5 (HIGH) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
  • (A CVSS v4.0 score of 8.7 has also been published for this CVE: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N)

Mitigation and recommended actions

  • Immediate: No official patched release has been identified as of this writing. Monitor the vendor’s GitHub repository for a fix and upgrade as soon as one is published.
  • If no patch is available:
    • Restrict or validate the url parameter server-side with a strict allowlist of permitted destination hosts/domains.
    • Block outbound requests from the application host to internal/private IP ranges and cloud metadata endpoints (e.g., 169.254.169.254) using egress filtering or a network proxy.
    • Place the service behind a WAF or reverse proxy that can inspect and restrict SSRF-style parameters.
    • Avoid exposing the affected endpoints directly to the internet where not required; limit access to trusted networks.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: Douyin_TikTok_Download_API, Douyin/TikTok online parsing and download without watermark
  • Raw response body: pywebio-loading

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge