Applications

CVE-2026-60037

8.6

High

EPSS n/aPatch available

Authenticated high-privilege RCE via OpenSSL code injection in device-importer frontend

exploited

No known exploitation not in CISA KEV as of our last sync

fix

Patch available see the advisory in the references

likelihood

No EPSS score yet

Published 10 Nov 2026Analysed here 10 Nov 2026CVSS scored by the publisher (CNA)

common questions

Is CVE-2026-60037 being exploited?

Not confirmed. CVE-2026-60037 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.

How severe is CVE-2026-60037?

CVE-2026-60037 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-60037?

Yes. A fix has been recorded for CVE-2026-60037. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-60037 affect?

CVE-2026-60037 affects Frontends device-importer component, Products using OpenSSL-based device importers, Vendor front-end appliances with device-import functionality. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-60037?

Identify exposed device-importers, restrict privileged accounts, block access, and apply vendor patch when released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary

technical analysis

affected

Frontends device-importer componentProducts using OpenSSL-based device importersVendor front-end appliances with device-import functionality

impact

Authenticated high-privilege remote code execution via OpenSSL injection, allowing full system compromise and data loss.

action required

Immediate action required

affected versions

MB connect line mbCONNECT24

affected>= 2.0.0 and < 2.21.0

MB connect line mymbCONNECT24

affected>= 2.0.0 and < 2.21.0

Helmholz myREX24V2

affected>= 2.0.0 and < 2.21.0

Helmholz myREX24V2.virtual

affected>= 2.0.0 and < 2.21.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

timeline

10 Nov 2026Published
10 Nov 2026CVE record last updated · same day later
10 Nov 2026Analysed by vulneraibility.com · same day later

how to fix

Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.

references

NVD CVE.org CVE Details Source

2 references in the CVE record: 2 links

Linkcertvde.com /en/advisories/VDE-2026-079/
Linkcertvde.com /en/advisories/VDE-2026-141/

sources

CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
NVD: CVSS and CPE data
FIRST EPSS: exploit probability and percentile
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free