Transmission 4.1.4 fixes potential macOS code execution and hardens RPC
What Transmission 4.1.4 fixes on macOS, in torrent-add RPC and Windows dependencies, plus compatibility and upgrade checks.
Upgrade to Transmission 4.1.4 if your system supports it. The release fixes a potential code-execution issue in the macOS client, hardens torrent-add requests to the remote-control API, and updates Windows dependencies. Transmission explicitly encourages users to upgrade in its release notes. These are application-security fixes, not changes that hide your IP address from other peers.
macOS: code execution requires local preference access
The most important distinction is the attack prerequisite. Transmission describes the macOS issue as a “potential RCE vulnerability” but says it requires local write access to the user’s preferences and is not remotely exploitable. Do not read the RCE label as evidence that an arbitrary torrent peer can execute code on your Mac. The macOS release notes identify the issue as GHSA-v7mp-fpv3-jf5r.
For Mac users, there is also a compatibility change: 4.1.4 requires macOS 12 or later. Check your OS version before replacing the application. If your Mac cannot run macOS 12, this build is not a supported upgrade path. The official download page confirms the requirement.
All platforms: malformed torrent-add RPC requests
The all-platform hardening concerns RPC—the API used to control a Transmission session—not the ordinary BitTorrent peer connection.
Pull request #9158, merged on October 20, 2026, describes a potential buffer overflow involving file-priority arguments in a torrent-add request. An out-of-range value could cause a write beyond the end of the file-priority buffer. The change also adds locking around a method exposed through the C API and called by application code from other threads.
That establishes a concrete memory-safety fix. The pull request does not demonstrate a successful remote code-execution attack; the release notes describe the change as hardening against malformed requests.
If you run Transmission on a NAS, server or container, update the running Transmission backend, not merely the browser interface or remote-control application. A patched remote client is not a substitute for updating the process handling requests. Keep the RPC service restricted to intended users and networks: Transmission’s RPC specification documents authentication as optional, so installing the update is not a reason to assume access is authenticated.
Windows dependencies and a TLS-verification fix
The Windows Qt builds move from zlib 1.3.1 to 1.3.2 to incorporate fixes from a 7ASecurity audit. They also update Qt to 6.10.3 for Windows 10+ builds and 5.15.19 for Windows 7 builds. Transmission’s release notes describe the Qt updates as bugfixes; they do not label every dependency change a security fix. The zlib update pull request also identifies the audit findings as the reason for that update.
Another all-platform fix addresses a bug where setting TR_CURL_PROXY_SSL_NO_VERIFY broke origin-server SSL verification. If you use that environment variable, this is an additional reason to update—not a recommendation to disable certificate verification. See the TLS-verification fix.
What to check after upgrading
- Get desktop installers from the official downloads page. For packaged or container installations, check the maintainer’s available version and patch notes.
- Restart the application or service and verify the version of the process actually running. For remote setups, check the server, not just the controller.
- Keep remote-access controls in place. The earlier Transmission 4.1.3 remote-access security guide covers the separate CORS/session-ID fix and access checks.
Patching does not change the basic connection-privacy boundary. The BitTorrent specification describes peer lists containing IP addresses and ports; 4.1.4 does not introduce an IP-hiding mechanism. For that separate exposure question, see what other peers can see.