Quick answers
- Is CVE-2026-82041 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82041 being exploited in the wild.
- How severe is CVE-2026-82041?
- Critical severity, with a CVSS score of 9.9, published 2 October 2026.
- Which products and versions are affected?
- UTMStack before 11.2.16.
- Is there a fix for CVE-2026-82041?
- Yes: fixed in 11.2.16. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-82041 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-82041?
- Check whether you run UTMStack at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 11.2.16
Technical details
The UTMIncidentCommandWebsocket.processCommand() handler, mapped to the /command/{hostname} STOMP destination, fails to enforce role-based access control or command validation before forwarding commands via gRPC to connected agents. An authenticated attacker can send arbitrary OS commands regardless of their assigned role; agents commonly execute with root or SYSTEM privileges, granting full system compromise.
Affected products
- UTMStack UTMStack before 11.2.16
Timeline
- 2026-10-02: disclosed
- 2026-10-01: patched