Skip to content
IoT

CVE-2026-14837

8.5
High
EPSS 0.08%Patch availableJul 27, 2026

Local signature bypass lets attackers enable SSH and gain admin access on Lenze devices.

common questions

Is CVE-2026-14837 being exploited?

Not confirmed. CVE-2026-14837 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. EPSS currently estimates a 0.08% probability of exploitation in the next 30 days.

How severe is CVE-2026-14837?

CVE-2026-14837 is rated High with a CVSS score of 8.5. 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-14837?

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

What does CVE-2026-14837 affect?

CVE-2026-14837 affects Lenze industrial devices, Embedded SSH enablement mechanism, Lenze controllers/drives/HMI. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-14837?

Restrict local access, disable SSH enablement, 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
Lenze industrial devicesEmbedded SSH enablement mechanismLenze controllers/drives/HMI
impact

Local low-priv attacker can bypass SSH enable file signature, enable SSH, gain administrative access and fully compromise the device.

action required

Immediate action required

affected versions
Lenze c430
  • affected>= 1.0.0 and < 1.15.2
Lenze c520
  • affected>= 1.0.0 and < 1.15.2
Lenze c550
  • affected>= 1.0.0 and < 1.15.2
Lenze i950 GenA
  • affected>= 1.0.0 and < 1.14.2
Lenze i950 GenB
  • affected>= 2.0.0 and < 2.0.3

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.

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
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free