cve.bz

CVE-2026-116748 transmission transmission

8.7 highEPSS 1.2%

High (8.7) in transmission transmission. EPSS 1.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

8.7 high
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

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
1.2% (unchanged from 1.2% a week ago) estimated probability of exploitation activity in the next 30 days; 70th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-31. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-942 Permissive Cross-domain Security Policy with Untrusted Domains
OWASP Top 10
A02:2025 Security Misconfiguration
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-116748 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-116748?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-116748?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-116748 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
transmissionfrom 4.0.0 before 4.1.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13transmissionno fix listedDEBIAN-CVE-2026-116748
Debian14transmission4.1.3+dfsg-1DEBIAN-CVE-2026-116748
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 4 moretransmissionno fix listedUBUNTU-CVE-2026-116748

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as Important because an attacker can achieve code execution or data destruction in the context of the user running Transmission by leveraging cross-origin requests from a malicious webpage. While exploitation requires user interaction to visit a compromised site, the lack of origin validation allows direct compromise of the remote procedure call service without prior system access. Transmission is not included in core Red Hat Enterprise Linux releases, limiting exposure primarily to Extra Packages for Enterprise Linux (EPEL) and Fedora environments.

Red Hat's mitigation

--- CME Mitigation Guidance (2026-11-02) ---

Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.

The highest-value action is to eliminate permissive CORS header emission and enforce strict origin validation on the Transmission RPC server: upgrade to Transmission 4.1.3 (or the fixed Transmission builds), which remove CORS header emissions from RPC responses and warn at startup if both IP whitelisting and RPC authentication are disabled, closing all 3 injection vectors (cross-origin handshake session ID theft, unauthorized RPC command replay, malicious script-torrent-done execution). Until patched, this is a concern on hosts running Transmission RPC server reachable from the victim browser, so disable the Transmission RPC server when remote management is unneeded, enable RPC authentication, and restrict browser access to the RPC endpoint. As a compensating measure, Disable the Transmission RPC service when remote management is not required, Deploy EDR agents to detect and terminate malicious child process executions spawned by Transmission via script-torrent-done abuse, and Configure Falco or eBPF runtime security to detect anomalous process spawning or shell executions initiated by transmission-daemon. These controls limit blast radius and contain exploitation, but they do not fix the underlying overly permissive CORS policy defect — apply the upstream patch to fully remediate.

Highest-impact CME: CME-914 Strict CORS Origin Allowlist Enforcement (high)

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-116748.

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

References

Check your stackJSON