yt-dlp versions from 2.10.5 up to but not including 2.10.5_7 included DouyuTV and DouyuShow extractors that fetched a component of the crypto-js JavaScript library from a third-party CDN (cdn.bootcdn.net) controlled by a known malicious actor. This JavaScript code was executed externally using PhantomJS, potentially exposing users to malicious code execution if certain conditions were met. The issue is fixed in yt-dlp version 2024.07.07 by removing the malicious CDN URL and invalidating cached data.
yt-dlp's --exec option is vulnerable to arbitrary command injection when unsafe string formatting conversions are used in the command template. This allows an attacker to execute arbitrary shell commands via maliciously crafted video metadata. The vulnerability affects users who use unsafe conversions like %()s in --exec templates. yt-dlp 2026.06.09 fixes this by restricting allowed conversions to safe ones and limiting characters in templates. Users can mitigate by upgrading or avoiding unsafe conversions or the --exec option altogether.
A Unicode normalization mismatch in setuptools' handling of MANIFEST.in exclusions can cause files intended to be excluded from source distributions to be included instead. This occurs on macOS APFS/HFS+ filesystems where filenames are stored in NFD form but MANIFEST.in patterns are typically in NFC form, leading to silent exclusion bypasses. This can result in unintended disclosure of sensitive files when publishing to PyPI.
A path traversal vulnerability in setuptools' PackageIndex.download function allows an attacker to write files to arbitrary filesystem locations with the permissions of the running process. The flaw arises from insufficient sanitization of URL-derived filenames used in os.path.join, enabling path traversal despite some replacement of '..' sequences. This vulnerability was fixed in setuptools version 1.17.0_1. Exploitation could lead to arbitrary file write and potentially remote code execution depending on context. The affected component is deprecated, reducing the attack surface.
Webpack versions from 5.49.0 up to but not including 5.104.0 have a vulnerability in the HttpUriPlugin when experiments.buildHttp is enabled. The plugin enforces allowedUris only on the initial URL but fails to re-validate after HTTP redirects, allowing bypass of the allow-list. This can lead to build-time SSRF and inclusion of untrusted content in build outputs. The issue is fixed in version 5.104.0.
Webpack versions from 5.49.0 up to but not including 5.104.1 have a vulnerability in the HTTP(S) resolver when experiments.buildHttp is enabled. This flaw allows bypassing the allowedUris allow-list by using URLs with userinfo (username:password@host), leading to build-time SSRF and untrusted content inclusion. The issue is patched in version 5.104.1.
CVE-2025-66034 is an arbitrary file write vulnerability in the fontTools.varLib component used by WeasyPrint. It arises from unsanitized filename handling and XML injection in .designspace files, allowing attackers to write files to arbitrary filesystem locations and inject malicious content. This can lead to remote code execution without elevated privileges and potential privilege escalation by overwriting critical system files. The vulnerability affects fontTools.varLib versions >=61.0 and <66.0_2 and has been fixed in version 66.0_2.
Scrapy versions up to 2.13.3 are vulnerable to a denial of service (DoS) attack due to a flaw in the brotli decompression implementation. The existing protection against decompression bombs does not mitigate the brotli variant, allowing remote servers to cause clients to crash by consuming excessive memory during decompression. This vulnerability is fixed in version 66.0_1 of Weasyprint.
The Vite development server option `server.fs.deny` can be bypassed on case-insensitive filesystems, such as Windows, by using case-augmented filenames. This allows an attacker to access files that are intended to be blocked by the deny list. The issue arises because the underlying glob matching is case-sensitive, while the filesystem is not, enabling blacklist bypass. This vulnerability affects Vite versions from 2.7.0 up to but not including 5.0.12 and has been fixed in 5.0.12 and earlier patch releases of prior major versions.
Vite's development server option `server.fs.deny` did not properly deny requests for patterns that include directories, such as `/foo/**/*`. This issue affects applications that customize `server.fs.deny` with directory patterns and expose the Vite dev server to the network. The vulnerability arises from the use of picomatch with the `matchBase: true` option, which only matches basenames and not full paths, allowing unauthorized access to files under denied directories like `.git`. This flaw was fixed in multiple Vite versions starting with 2.9.18, 3.2.10, 4.5.3, 5.0.13, 5.1.7, and 5.2.6.
Vite versions from 2.5.1 up to but not including 5.4.6 contain a vulnerability where the server's file system access restrictions can be bypassed using the '?import&raw' query parameters. This allows an attacker to retrieve the contents of arbitrary files outside the intended serving allow list. The vulnerability has a medium severity with a CVSS score of 5.3.
A DOM Clobbering vulnerability in Vite affects bundled scripts built with output formats cjs, iife, or umd. This flaw allows an attacker to manipulate the document.currentScript property by injecting a scriptless HTML element named 'currentScript', causing the application to load attacker-controlled scripts dynamically. This can lead to cross-site scripting (XSS) in web pages that include vulnerable Vite bundles and allow embedding of such HTML elements. The vulnerability impacts Vite versions from 2.5.1 up to but not including 5.4.6. A fix is available.
Vite development server versions from 2.5.1 up to but not including 6.0.9 have a vulnerability that allows any website to send requests to the dev server and read responses due to permissive default CORS settings and lack of Origin header validation on WebSocket connections. This affects even local-only dev servers. The vulnerability can expose sensitive development files to malicious websites. A fix is available in newer Vite versions. Mitigations include configuring CORS origins, allowed hosts, and using HTTPS or updated browsers. Some mitigations are not possible without upgrading.
A vulnerability in Vite allows bypassing the server.fs.deny restriction when using the ?raw?? or ?import&raw?? query parameters, enabling access to arbitrary file contents. This affects Vite dev servers explicitly exposed to the network via the --host option or server.host configuration. The issue arises because trailing separators in the query string are removed inconsistently, allowing unauthorized file reads outside the allowed serving paths. A proof of concept demonstrates reading sensitive files such as /tmp/secret.txt. The vulnerability affects Vite versions from 2.5.1 up to but not including 6.2.3. A patch is available to address this issue. The CVSS score is 5.3 (medium severity).
Vite versions from 2.5.1 up to but not including 6.2.5 have a vulnerability that allows arbitrary file contents to be returned to the browser. This occurs when the Vite development server is exposed to the network using the --host option or server.host configuration. The vulnerability involves bypassing the server.fs.deny restriction via requests ending with .svg or using relative paths before normalization. The issue affects files smaller than the default 4kB inline asset limit in Vite 6.0 and later. Exploitation requires network access to the dev server and user interaction (UI:R).
Vite versions from 2.5.1 up to but not including 6.2.6 have a vulnerability in the dev server's file system access control. When running on Node or Bun runtimes and explicitly exposed to the network, specially crafted HTTP requests with an invalid request-target containing a '#' character can bypass the server.fs.deny check. This allows an attacker to retrieve arbitrary files from the server. The vulnerability does not affect Vite running on Deno due to different URL handling. A proof-of-concept demonstrates reading sensitive files like /etc/passwd via this bypass.
Nu Html Checker (vnu) versions prior to 26.8.6 contain a Server-Side Request Forgery (SSRF) vulnerability. This flaw allows remote attackers to bypass hostname-based restrictions and make the server perform arbitrary HTTP/HTTPS requests to internal resources, including localhost. The vulnerability is due to the ability to bypass protections using DNS rebinding or domains resolving to loopback addresses. A patch is available to fix this issue.
Vdirsyncer versions from 0.19.0 up to but not including 0.19.2_4 are affected by a vulnerability in a dependency, aiohttp, which uses llhttp 8.1.1. This version of llhttp is vulnerable to two request smuggling vulnerabilities. The issue is resolved by upgrading to llhttp 9 or later, which is included in aiohttp 3.8.6 and newer.
Starlette's StaticFiles component on Windows platforms has a vulnerability where resolving UNC paths triggers outbound SMB connections, leaking NTLMv2 credentials. This occurs because os.path.realpath resolves UNC paths before containment checks, causing server-side request forgery (SSRF). The vulnerability affects default configurations (follow_symlink=False) and can expose service account credentials to attackers. Non-Windows systems and configurations using follow_symlink=True are not affected. Mitigations include using dedicated web servers for static files or blocking outbound SMB traffic.
A vulnerability in the MCP Python SDK HTTP transports (SSE and Streamable HTTP in stateful mode) allows session hijacking by bypassing authentication checks. Incoming requests are routed to existing sessions based solely on session IDs without verifying the authenticated principal. This enables an attacker who knows or guesses a session ID to send JSON-RPC messages on that session regardless of the bearer token used. The issue affects versions from 0.4.3 up to but not including 0.5.17. A fix is available in version 1.27.2 or later.