Black Friday60% off BLACKFRIDAY2026
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
medium·Misconfiguration·Updated Nov 9, 2026

CVE-2026-116748 Scanner

CVE-2026-116748 Scanner - Cross-Site Request Forgery (CSRF) vulnerability in Transmission

Est. Time~10 seconds
Scan TypeSingle Scan
Targetsurl
CostFree
5
Times Used
continuous scan runs
4.2k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
8.7
CVSShigh
Exploitable remotely over the internet · no authentication required.
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.

Attack Vector
Network
Privileges Req.
None
User Interaction
P
Affected
transmissionby transmission
AFFECTED< 4.1.3→SAFE ✓≥ 4.1.3
Updated Nov 6, 2026View on NVD →
Detail

Transmission is a software application used widely for peer-to-peer file sharing via the BitTorrent protocol. It is commonly utilized by individuals and organizations for downloading and sharing large files efficiently. The application is cross-platform, supporting various operating systems including Windows, macOS, and various Linux distributions. Due to its ease of use and open-source nature, Transmission is a popular choice among developers and end-users alike. It features a web-based interface, allowing users to manage torrent downloads remotely. This functionality makes Transmission a valuable tool for users looking to manage their downloads over a network or the internet.

Cross-Site Request Forgery (CSRF) is a vulnerability that can occur in web applications when they fail to verify the authenticity of requests received from a client. This particular vulnerability affects versions 4.0.0 through 4.1.2 of the Transmission application. Due to permissive CORS settings, an attacker could gain unauthorized control over the RPC API of the Transmission daemon by reading the session-id nonce. This enables attackers to perform actions such as executing scripts, changing download directories, or deleting torrents and data without the user's consent. The vulnerability represents a significant breach of the security concept called "same-origin policy", which is crucial for web application security.

The vulnerability arises from Transmission improperly setting the CORS headers on RPC responses, specifically by sending "Access-Control-Allow-Origin: *" and exposing the "X-Transmission-Session-Id" via "Access-Control-Expose-Headers". These settings allow any website visited by the user to capture the session ID, which is typically used to prevent CSRF attacks. The exploitable endpoint is the RPC API of Transmission, where the attacker can use the captured session ID to manipulate the application. This flaw could be leveraged to perform a variety of unauthorized actions, significantly impacting data integrity and availability. An affected endpoint is "{{BaseURL}}/transmission/rpc", where the vulnerability manifests.

Exploitation of this vulnerability allows attackers to perform unauthorized actions within the Transmission application. When exploited, attackers can change configuration settings, delete or modify torrents without user consent, and execute RPC calls that may compromise the integrity of torrent downloads. The unauthorized control of the RPC API could lead to potential data loss or tampering, representing a considerable risk to users relying on Transmission for managing substantial data transfers. Moreover, the exposure of the session ID can be further exploited for subsequent attacks within the browser context. The ongoing unauthorized access can lead to significant disruptions in service and data management.

REFERENCES

Solution Advice
  • Upgrade to Transmission version 4.1.3 or later to address this security vulnerability.
  • Implement stronger CORS configurations and remove unnecessary CORS headers from response.
  • Restrict access to the RPC interface by utilizing a whitelist and enabling proper authentication mechanisms.
  • Regularly audit and review RPC access logs to detect unauthorized attempts or suspicious activity.
  • Educate users on the risks associated with cross-origin requests to enhance awareness and compliance.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

12,000+ scanners. Free to start. No credit card required.