OpenSSL command injection in device importer
- Exploited
- No known exploitation
- Fix
- Fixed in 2.21.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.21.0.
- 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
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.49% · 42nd percentile
- 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? →
- 13/100 · provisional
- 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
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
The OpenSSL command injection in the device importer affects the frontend and lets a remote attacker who already has high privileges run code on the system, with full loss of confidentiality, integrity, and availability. The attacker can reach it over the network, but they must log in with high privileges first.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
A high privileged remote attacker can perform an OpenSSL code injection in the frontends device importer function leading to code execution. This can result in a total loss of confidentiality, integrity and availability.
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.6/10CVSS 8.6, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2.21.0.
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-60037 (OpenSSL command injection in device importer), 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-60037 (entry last updated 2026-11-10): Affected: - MB connect line mbCONNECT24: from 2.0.0, fixed in 2.21.0 - MB connect line mymbCONNECT24: from 2.0.0, fixed in 2.21.0 - Helmholz myREX24V2: from 2.0.0, fixed in 2.21.0 - Helmholz myREX24V2.virtual: from 2.0.0, fixed in 2.21.0 Fixed versions: 2.21.0. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-60037 is not listed as of cve.now's last read. This KEV status is for CVE-2026-60037 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://www.certvde.com/en/advisories/VDE-2026-079/ - https://www.certvde.com/en/advisories/VDE-2026-141/ 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-60037 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-60037.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- MB connect line mbCONNECT24
From 2.0.0 · fixed in 2.21.0
- MB connect line mymbCONNECT24
From 2.0.0 · fixed in 2.21.0
- Helmholz myREX24V2
From 2.0.0 · fixed in 2.21.0
- Helmholz myREX24V2.virtual
From 2.0.0 · fixed in 2.21.0
Evidence 4
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 2
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-60037
Is CVE-2026-60037 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
Which versions are affected by CVE-2026-60037?
mbCONNECT24: from 2.0.0 before 2.21.0. mymbCONNECT24: from 2.0.0 before 2.21.0. myREX24V2: from 2.0.0 before 2.21.0. myREX24V2.virtual: from 2.0.0 before 2.21.0.Source: cve.now feed data
How do I fix CVE-2026-60037?
Upgrade to a fixed version: 2.21.0.Source: cve.now feed data