Quick answers
- Is CVE-2026-60041 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-60041 being exploited in the wild.
- How severe is CVE-2026-60041?
- High severity, with a CVSS score of 8.1, published 10 November 2026.
- Which products and versions are affected?
- Helmholz myREX24V2 before 2.21.0; Helmholz myREX24V2.virtual before 2.21.0.
- Is there a fix for CVE-2026-60041?
- Yes: fixed in 2.21.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-60041 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-60041?
- Check whether you run Helmholz myREX24V2 or Helmholz myREX24V2.virtual 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: 2.21.0
Technical details
An unauthenticated attacker can craft a malicious webpage that, when visited by an authenticated backend user, performs unauthorized actions via cross-site request forgery (CSRF). The vulnerability affects the myREX24V2 firmware and allows execution of critical system operations (shutdown, backup restore) without authentication checks on the request. The attack requires the victim to be logged in but no other preconditions.
Affected products
- Helmholz myREX24V2 before 2.21.0
- Helmholz myREX24V2.virtual before 2.21.0
Timeline
- 2026-11-10: disclosed