CVE-2025-69517: tacticalrmm · n/a
Affects tacticalrmmSource CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 28 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubamidaware/tacticalrmmpkg:github/amidaware/tacticalrmmOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
European organizations should immediately audit their Tactical RMM deployments to identify affected versions (1.3.1 and earlier). Since no official patches are currently available, organizations should implement compensating controls such as restricting access to the new agent creation API endpoint to only highly trusted users and monitoring for unusual agent creation activity. Administrators should be trained to recognize suspicious UI behavior in the management panel and avoid interacting with untrusted agents. Network segmentation and strict access controls should be enforced to limit exposure of the Tactical RMM interface. Implement multi-factor authentication (MFA) for all users with access to Tactical RMM to reduce the risk of credential compromise. Additionally, organizations should consider deploying web application firewalls (WAFs) with custom rules to detect and block suspicious HTML payloads in agent creation requests. Continuous monitoring and logging of administrative actions within Tactical RMM can help detect exploitation attempts. Finally, maintain close communication with Amidaware Inc for updates on official patches or security advisories.
Description
An HTML injection vulnerability in Amidaware Inc Tactical RMM v1.3.1 and earlier allows authenticated users to inject arbitrary HTML content during the creation of a new agent via the POST /api/v3/newagent/ endpoint. The agent_id parameter accepts up to 255 characters and is improperly sanitized using DOMPurify.sanitize() with the html: true option enabled, which fails to adequately filter HTML input. The injected HTML is rendered in the Tactical RMM management panel when an administrator attempts to remove or shut down the affected agent, potentially leading to client-side attacks such as UI manipulation or phishing. NOTE: the Supplier's position is that this has incorrect information.