Transmission 4.1.3 closes a remote-access CSRF gap
What Transmission 4.1.3 fixes in remote access, why the session-ID leak matters, and which authentication and network settings still need checking.
A webpage you visit should not be able to read the security token protecting Transmission’s remote-control interface. Transmission 4.1.3 fixes a bug that allowed that token to leak through permissive browser-access headers. If you enable remote access, update the Transmission instance serving it—not just the app you use to control it. The project’s 4.1.3 release notes describe a potential cross-site request forgery (CSRF) issue and encourage users to upgrade.
The update repairs one browser security boundary. It does not make an unauthenticated, openly reachable control interface safe.
What leaked, and why it matters
Transmission’s RPC interface is the API used to control a running session. Its CSRF protection normally requires an X-Transmission-Session-Id header. Once other access checks pass, a request with a missing or incorrect token receives HTTP 409, with the correct token in the response headers; a legitimate client then retries using that value. That handshake is documented behavior, not itself a vulnerability.
The problem was who could read the response. According to the fix’s explanation, the RPC server:
- Sent
Access-Control-Allow-Origin: *. - Reflected requested headers during CORS preflight handling.
- Exposed
X-Transmission-Session-Idto browser scripts on the409response.
CORS—Cross-Origin Resource Sharing—controls whether scripts on one website can read responses from another origin. Those permissive headers let a visited webpage read the nonce intended to guard against forged requests.
The nonce is not your RPC password. Leaking it weakens the CSRF defense; it does not establish that every password-protected installation can be taken over. Practical exposure also depends on whether the browser can reach the RPC service and whether its other access checks permit the requests.
Version 4.1.3 removes the CORS headers, rather than removing the token handshake. The maintainers say the bundled Web UI and non-browser clients remain supported; cross-origin browser reads are blocked. A separately hosted browser dashboard may therefore need adjustment. Do not restore broad CORS permissions simply to make it work again. (Fix details)
Settings to check after upgrading
Use this as a remote-control checklist, not a peer-connection checklist.
1. Update and restart the server instance
Check the version reported by the running Transmission server after updating and restarting it. Updating a desktop remote-control client does not patch a separate daemon on a NAS, container or other computer. Version 4.1.3 contains this fix; do not assume an older package contains it unless its distributor documents a backport.
2. Disable remote control if you do not need it
For JSON-configured installations, the setting is rpc-enabled: false in Transmission 4’s default configuration format. If remote control is needed only locally, consider setting rpc-bind-address to 127.0.0.1 rather than listening on all network interfaces. A local bind limits network reachability; it is not a reason to skip the update.
Transmission 4.1.3’s documentation uses underscore names such as rpc_enabled and rpc_bind_address, but explicitly says hyphenated names remain the default in Transmission 4. Match the format already used by your installation. Close the client or stop the daemon before editing its settings file, so your changes are not overwritten. (Configuration documentation)
3. Require authentication and restrict allowed addresses
For the default Transmission 4 JSON format, review:
| Setting | Recommended purpose |
|---|---|
rpc-authentication-required |
Set to true for remote control. |
rpc-username, rpc-password |
Configure dedicated credentials with a strong, unique password. |
rpc-whitelist-enabled |
Keep enabled where practical. |
rpc-whitelist |
Allow only the management addresses you need, rather than a broad wildcard. |
These hyphenated keys are listed in the older-format documentation referenced by the 4.1.3 guide. The IP whitelist and password are separate controls. If entering a plaintext password directly in the settings file, do not start it with {: Transmission treats that prefix as indicating an already salted password.
The fix also adds a warning when authentication and the IP whitelist are both disabled: anyone who can reach the RPC server has full control. That is a warning, not automatic protection—the update does not enable a password or whitelist for you. (Patch)
4. Protect the management connection
Avoid exposing RPC directly to the public internet. For access from elsewhere, prefer a restricted private management connection, such as an SSH tunnel or private VPN, and retain authentication.
Transmission uses HTTP Basic authentication. Base64 encoding does not encrypt the credentials, so protect any network path carrying them with HTTPS/TLS or an encrypted tunnel. (Transmission authentication specification; Basic authentication security)
If you use a reverse proxy, check that it does not reintroduce permissive CORS headers, and that the backend RPC port cannot bypass the intended access restrictions. Also keep rpc-host-whitelist-enabled enabled and add only required names to rpc-host-whitelist: this provides a separate DNS-rebinding defense, not an IP allowlist or password replacement.
Verify the boundary you intended
After restarting, confirm that your legitimate management client still works, a fresh connection without credentials cannot perform RPC operations, and devices outside your intended management network cannot reach the interface. Do not use a browser session that has already authenticated as your no-credentials check. Check the daemon log for the new no-password/no-whitelist warning. A 409 token-handshake response alone is neither proof of compromise nor proof that authentication is configured correctly.
This release protects the control interface, not the address visible in BitTorrent traffic. Keep that separate from what other peers can see: repairing remote-access CSRF does not hide your peer-facing IP address.