CVE-2026-38978
Received Received - Intake
Clickjacking Vulnerability in Transmission WebUI

Publication date: 2026-06-02

Last updated on: 2026-06-02

Assigner: MITRE

Description
transmission through 4.1.1 was found to have a clickjacking weakness in the browser-facing WebUI and RPC response paths.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-02
Last Modified
2026-06-02
Generated
2026-06-02
AI Q&A
2026-06-02
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
transmission transmission to 4.1.1 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability impact me? :

This vulnerability can lead to unauthorized actions being performed on the Transmission WebUI or RPC interface without the user's knowledge.

An attacker could craft a malicious webpage that embeds the Transmission interface in a hidden frame and trick an authenticated user into clicking on elements that trigger unintended commands or changes.

Such unintended actions could compromise the security or functionality of the Transmission client, potentially leading to misuse or disruption of the BitTorrent client.


Can you explain this vulnerability to me?

CVE-2026-38978 is a clickjacking vulnerability found in Transmission version 4.1.1 affecting its browser-facing WebUI and RPC response paths.

Clickjacking is a malicious technique where an attacker tricks a user into clicking on something different from what the user perceives, often by embedding the targeted interface inside a hidden or disguised frame on a malicious webpage.

In this case, the Transmission WebUI and RPC responses lacked anti-clickjacking HTTP headers such as "X-Frame-Options" and "Content-Security-Policy: frame-ancestors", which would normally prevent the interface from being embedded in frames on other sites.

Because these headers were missing, an attacker could embed the Transmission management interface in a frame on a malicious site and trick authenticated users into performing unintended actions.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by inspecting the HTTP response headers of the Transmission WebUI and RPC interfaces to check for missing anti-clickjacking headers.

  • Use a command like curl to fetch the HTTP headers from the Transmission WebUI or RPC endpoint, for example: curl -I http://<transmission-host>:<port>/transmission/web/
  • Check if the response headers include "X-Frame-Options" with a value such as "SAMEORIGIN" and "Content-Security-Policy" with a "frame-ancestors 'self'" directive.
  • If these headers are missing, the system is vulnerable to clickjacking attacks as described in CVE-2026-38978.

What immediate steps should I take to mitigate this vulnerability?

To mitigate this vulnerability, ensure that the Transmission WebUI and RPC responses include appropriate anti-clickjacking headers.

  • Update Transmission to version 4.1.2 or later, where the fix adding the headers "X-Frame-Options: SAMEORIGIN" and "Content-Security-Policy: frame-ancestors 'self'" has been applied.
  • If updating is not immediately possible, consider implementing a reverse proxy or web server configuration that adds these headers to the HTTP responses serving the Transmission WebUI and RPC interfaces.
  • Restrict access to the Transmission WebUI and RPC interfaces to trusted networks or users to reduce exposure.

How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability involves a clickjacking weakness in Transmission's WebUI and RPC response paths, which could allow attackers to trick authenticated users into unintended actions. While the provided information does not explicitly mention compliance with standards like GDPR or HIPAA, clickjacking vulnerabilities can potentially lead to unauthorized actions or data exposure, which may impact compliance with security requirements in these regulations.

The fix adds security headers to prevent framing of the interface, aligning with OWASP recommendations and improving security posture. This mitigation helps reduce risks that could otherwise contribute to non-compliance with security controls mandated by common standards.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart