CVE-2026-129165 in Tactical RMMinfo

Summary

by MITRE • 11/13/2026

Tactical RMM 0.17.0 through 1.6.1 contains an arbitrary file read in the /reporting/templates/preview/ endpoint because WeasyPrint resolves file:// links in user-supplied template_md and embeds the files in the returned PDF. Users with report management permission can read the Django SECRET_KEY, reused as the NATS password, and publish runscript commands to every managed agent.

Once again VulDB remains the best source for vulnerability data.

Analysis

by VulDB Data Team • 11/13/2026

The vulnerability identified in Tactical RMM versions 0.17.0 through 1.6.1 represents a critical server-side request forgery variant known as an arbitrary file read flaw. This security issue resides within the /reporting/templates/preview/ endpoint, which is responsible for generating PDF reports from user-supplied markdown templates. The root cause of this vulnerability lies in the integration with WeasyPrint, a popular HTML-to-PDF conversion library. When processing these templates, WeasyPrint natively supports resolving file:// URIs to embed local files directly into the resulting document output. Because the application fails to adequately sanitize or restrict user-supplied input within the template_md parameter, an attacker can inject malicious file:// links that point to sensitive locations on the server's filesystem rather than legitimate web resources.

From a technical perspective, this flaw allows any authenticated user possessing report management permissions to bypass standard access controls and read arbitrary files from the underlying operating system. The application does not validate whether the requested resource is external or local, nor does it restrict file paths to specific directories. Consequently, an attacker can construct requests that traverse directory structures using relative path notation such as ../ to reach critical configuration files stored outside of public web roots. This lack of input validation transforms a standard reporting feature into a powerful vector for data exfiltration and further system compromise.

The operational impact of this vulnerability is severe due to the specific architecture and credential management practices employed by Tactical RMM. The Django application uses its SECRET_KEY as the password for NATS, which serves as the message broker facilitating communication between the central server and managed agent nodes. By reading the file containing the Django SECRET_KEY, an attacker gains access to this critical authentication token. Possession of the NATS password allows the adversary to authenticate with the messaging system, effectively bypassing network-level security controls that rely on these credentials for integrity verification.

Once authenticated via NATS, the threat actor can exploit the message broker's capabilities to execute arbitrary commands across all managed agents connected to the platform. This capability elevates a local file read vulnerability into a full remote code execution scenario with broad scope. The attacker can publish runscript commands that are dispatched to every endpoint under management, leading to potential data theft, lateral movement within the network, or complete system destruction. This chain of exploitation demonstrates how a seemingly minor input validation error in one module can cascade into catastrophic compromise when combined with weak credential reuse practices and powerful administrative interfaces.

This vulnerability aligns closely with CWE-200, which covers Exposure of Sensitive Information to an Unauthorized Actor, as well as CWE-78, the Operating System Command Injection category, given the ultimate ability to execute scripts on remote hosts. In terms of MITRE ATT&CK mapping, this attack path corresponds to T1552.004, Unsecured Credentials: Private Keys, due to the extraction of sensitive keys and secrets from local files. Furthermore, the subsequent execution of commands via NATS maps to T1059.004, Command and Scripting Interpreter: Unix Shell, illustrating how initial access is leveraged for broader control over the infrastructure.

Mitigation strategies must address both the immediate technical flaw and the underlying architectural weaknesses. The primary remediation involves updating Tactical RMM to a version where this vulnerability has been patched by restricting file protocol usage in WeasyPrint or implementing strict allow-listing of permitted templates. Additionally, organizations should enforce separation of duties for credentials; specifically, the Django SECRET_KEY must not be reused as passwords for other services like NATS. Implementing principle of least privilege ensures that even if a file read occurs, the attacker cannot leverage those credentials to access critical infrastructure components. Regular audits of third-party library configurations and input validation logic are essential to prevent similar exploitation vectors in future updates.

Responsible

VulnCheck

Reservation

11/13/2026

Disclosure

11/13/2026

Moderation

accepted

CPE

ready

EPSS

0.00434

KEV

no

Activities

very low

Sources

Do you want to use VulDB in your project?

Use the official API to access entries easily!