CVE-2026-116748

Transmission 4.0.0 before 4.1.3 Permissive CORS Leaks RPC Anti-CSRF Token

Published Oct 26, 2026 CVSS 4.0 · 8.7 High EPSS 1.2% KEV · Not listed
Description
Transmission 4.0.0 before 4.1.3 contains a permissive CORS vulnerability in handle_request() in rpc-server.cc that exposes the X-Transmission-Session-Id anti-CSRF token to any web origin. Malicious web pages can read the token from the 409 handshake response and replay it to issue RPC calls, enabling script-torrent-done execution, download-dir changes, or torrent and data deletion.

Analysis

AI-generated

Technical impact

Transmission’s rpc server implements a permissive CORS policy that permits any web origin to read the X-Transmission-Session-Id anti‑CSRF token from the 409 handshake response. This CWE-346 weakness allows an attacker to host a malicious webpage that first obtains the token, then uses it to issue RPC commands such as script‑torrent‑done, download‑dir changes, or torrent and data deletion. The flaw allows an attacker to control the Transmission daemon via cross‑origin requests; no local privileges are required beyond the user running the web browser.

Affected Systems

The vulnerability affects Transmission starting at version 4.0.0 and is present through all versions before 4.1.3. The product is the Transmission BitTorrent client; affected builds are those that expose the RPC interface without restricting the CORS origins.

Risk and Exploitability

The CVSS score of 8.7 labels this as a high‑severity flaw. The EPSS score is less than 1% (approximately 0.00527), indicating a very low exploitation probability, but the lack of a KEV listing does not diminish the risk. The likely attack vector is a victim who has Transmission’s RPC server running and enabled, and who visits a malicious webpage that can issue the cross‑origin request to the local or network‑visible RPC endpoint. The attacker can then replay the captured anti‑CSRF token to execute arbitrary RPC calls and modify or delete user data.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update Transmission to version 4.1.3 or later to receive the fixed CORS handling.
  • Restrict the RPC interface to the local host or a trusted internal network by configuring the server’s bind address or applying firewall rules, so that external web origins cannot reach it.
  • Disable or limit the permissive CORS settings in the Transmission configuration so that only specified origins may query the RPC endpoint if an upgrade cannot be performed immediately.

Generated by OpenCVE AI on October 30, 2026 at 14:11 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description Transmission 4.0.0 before 4.1.3 contains a permissive CORS vulnerability in handle_request() in rpc-server.cc that exposes the X-Transmission-Session-Id anti-CSRF token to any web origin. Malicious web pages can read the token from the 409 handshake response and replay it to issue RPC calls, enabling script-torrent-done execution, download-dir changes, or torrent and data deletion.
Title Transmission 4.0.0 before 4.1.3 Permissive CORS Leaks RPC Anti-CSRF Token
First Time appeared Transmissionbt
Transmissionbt transmission
Weaknesses CWE-942
CPEs cpe:2.3:a:transmissionbt:transmission:*:*:*:*:*:*:*:*
Vendors & Products Transmissionbt
Transmissionbt transmission
References
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 8.7, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-346

    Origin Validation Error

  • CWE-942

    Permissive Cross-domain Security Policy with Untrusted Domains

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 31, 2026, 2:02 AM
Reserved
Oct 26, 2026, 8:23 PM
Status
Awaiting Analysis
Published
Oct 26, 2026, 10:16 PM
Modified
Oct 31, 2026, 3:17 AM
Severity
Important
Public date
Oct 26, 2026, 9:52 PM