CVE
AmidaWare Tactical RMM arbitrary file read in report template preview
Affects Tactical RMM 0.17.0 through 1.6.1 for accounts that hold report management permission. The checked facts list no fixed version.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Tactical RMM versions 0.17.0 through 1.6.1 Attacker holds an account with report management permission
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 22/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
AmidaWare's Tactical RMM has an arbitrary file read flaw in its report template preview endpoint, reachable remotely over the network by a user who already has login access with report management permission. That user can read server files, including the Django SECRET_KEY, which is reused as the NATS password, and use it to publish run-script commands to every managed agent.
Read the original description
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.
Who should check
Teams running AmidaWare Tactical RMM 0.17.0 through 1.6.1, especially those with users holding report management permission on the RMM server.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.4/10CVSS 9.4
- No patch5/5No patch listed yet
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
- Would score about 29 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Tactical RMM versions 0.17.0 through 1.6.1 Attacker holds an account with report management permissionWorkaround: The checked facts give no workaround. Limiting report management permission to accounts that need it addresses the stated condition for this issue.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129165 (Tactical RMM 0.17.0 through 1.6.1 Arbitrary File Read via Report Preview), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129165 (entry last updated 2026-11-13):
Affected:
- AmidaWare Tactical RMM: from 0.17.0, through 1.6.1
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Tactical RMM versions 0.17.0 through 1.6.1 (source: https://vul.yulun.ac.cn/20261028/tacticalrmm/)
- Attacker holds an account with report management permission (source: https://vul.yulun.ac.cn/20261028/tacticalrmm/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-129165 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129165 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://vul.yulun.ac.cn/20261028/tacticalrmm/
- https://github.com/amidaware/tacticalrmm/blob/086e2d9714b1716796722c7e0c19a1ebe08a39f2/api/tacticalrmm/ee/reporting/utils.py#L110-L117
- https://github.com/amidaware/tacticalrmm/blob/086e2d9714b1716796722c7e0c19a1ebe08a39f2/api/tacticalrmm/ee/reporting/views.py#L202-L245
- https://github.com/amidaware/tacticalrmm/blob/086e2d9714b1716796722c7e0c19a1ebe08a39f2/api/tacticalrmm/tacticalrmm/utils.py#L227-L236
- https://www.vulncheck.com/advisories/tactical-rmm-0.17.0-through-1.6.1-arbitrary-file-read-via-report-preview
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129165
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129165"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- AmidaWare Tactical RMM
From 0.17.0 · through 1.6.1
Evidence 7
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 5
- Repository
- Repository
- Repository
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129165
Is CVE-2026-129165 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The report preview endpoint can read arbitrary files on the server. The advisory says this can expose the Django SECRET_KEY, and that the NATS bus password can then be used to send runscript commands to every managed agent.Source: vul.yulun.ac.cn
Which versions are affected by CVE-2026-129165?
Tactical RMM: from 0.17.0 through 1.6.1.Source: cve.now feed data
Am I affected, and how do I check?
Tactical RMM versions 0.17.0 through 1.6.1 are in the affected range. The advisory's stated condition is an account with report management permission. Compare your installed Tactical RMM version with that range.Source: vul.yulun.ac.cn
How do I fix CVE-2026-129165?
The checked facts name no fixed version or vendor patch, so no upgrade target can be given. Check the vendor's advisory for an update.Source: vul.yulun.ac.cn
What if there's no patch?
The checked facts give no workaround. Limiting report management permission to accounts that need it addresses the stated condition for this issue.Source: vul.yulun.ac.cn