Quick answers
- Is CVE-2026-60037 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-60037 being exploited in the wild.
- How severe is CVE-2026-60037?
- High severity, with a CVSS score of 7.2, published 10 November 2026.
- Which products and versions are affected?
- Helmholz myREX24V2 firmware < 2.21.0; Helmholz myREX24V2.virtual firmware < 2.21.0.
- Is there a fix for CVE-2026-60037?
- Yes: fixed in myREX24V2 firmware 2.21.0, myREX24V2.virtual firmware 2.21.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-60037 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-60037?
- 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: myREX24V2 firmware 2.21.0, myREX24V2.virtual firmware 2.21.0
Technical details
An OS command injection vulnerability exists in the frontends device importer function where OpenSSL operations are performed without proper input sanitization. A high-privileged remote attacker can inject arbitrary commands through this function to achieve code execution with full system privileges. The vulnerability requires high privilege access but results in complete system compromise.
Affected products
- Helmholz myREX24V2 firmware < 2.21.0
- Helmholz myREX24V2.virtual firmware < 2.21.0
Timeline
- 2026-11-10: disclosed