dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-20761

HIGH · 8.1 CVSS v3.1 Published 2026-02-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability exists in EnOcean SmartServer IoT version 4.60.009 and prior, which would allow remote attackers, in the LON IP-852 management messages, to send specially crafted IP-852 messages resulting in arbitrary OS command execution on the device.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The EnOcean SmartServer IoT versions 4.60.009 and prior contain a command injection vulnerability in the LON IP-852 protocol stack. Remote attackers can send specially crafted IP-852 management messages to achieve arbitrary OS command execution on the affected device.

MitigationApply vendor firmware updates when available. Until then, restrict network access to the SmartServer IoT management interface and implement network segmentation to limit exposure to untrusted networks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify SmartServer IoT device
    Locate EnOcean SmartServer IoT hardware on the network or in asset inventory. Check device hostname, MAC address OUI (EnOcean GmbH), or consult network scans for this device type.
    Affected if The device is an EnOcean SmartServer IoT unit
  2. Check firmware version
    Access the SmartServer IoT web interface (typically https://<device-ip>/) and navigate to System > Firmware or check via CLI using 'version' or 'show system info' command. Compare the displayed version to 4.60.009.
    Affected if Firmware version is 4.60.009 or lower
  3. Verify LON IP-852 protocol status
    In the SmartServer IoT web interface, navigate to Configuration > Protocols > LON or Network > LON IP-852 settings. Check if the LON IP-852 protocol stack is enabled and configured.
    Affected if LON IP-852 protocol is enabled and actively listening on port 1028/UDP (standard IP-852 port)
  4. Assess network exposure
    Review firewall rules and network access controls around the SmartServer IoT management interface and IP-852 port 1028/UDP. Determine if untrusted networks or the internet can reach these interfaces.
    Affected if Port 1028/UDP (IP-852) or the management web interface is exposed to untrusted networks

You are affected if you have a SmartServer IoT device running firmware 4.60.009 or lower with LON IP-852 enabled and port 1028/UDP reachable from untrusted networks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware updates when available. Until then, restrict network access to the SmartServer IoT management interface and implement network segmentation to limit exposure to untrusted networks.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-20761 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-20761 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data