Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Low

Out-of-bounds read memory leak in EnOcean SmartServer IoT IP-852 extended-header parsing

IdentifiersCVE-2026-22885CWE-125· Out-of-bounds Read

CVE-2026-22885 is an information disclosure vulnerability affecting EnOcean SmartServer IoT version 4.60.009 and earlier, and reportedly related legacy i.LON devices implementing the same IP-852/LonTalk handling. The flaw is in extended-header parsing for LON IP-852 management messages, specifically in LtIpPktHeader::parse in LtIpPackets.cpp. The parser trusts the user-controlled extndHdrSize field and advances the payload offset by extndHdrSize multiplied by four without sufficient bounds validation. Because incoming IP-852 packets are processed from a stack-based buffer, a specially crafted packet can cause the device to parse and later echo data from unintended stack memory rather than the intended payload. Claroty Team82 reported that the proprietary PKTTYPE_TIMESYNCHREQ (0xF1) request / PKTTYPE_TIMESYNCHRSP (0xF2) response path can be abused to disclose stack memory. This is consistent with an out-of-bounds read leading to a memory leak from process memory.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a remote, unauthenticated attacker to disclose memory from the target process, including stack contents. Reported leaked data may include runtime pointers that can be used to infer the base address of libLonStack.so and bypass ASLR, reducing exploit mitigations and potentially facilitating follow-on exploitation of other vulnerabilities such as remote code execution. The direct impact is confidentiality loss; integrity and availability impact appear limited based on the provided material, although repeated triggering could potentially contribute to instability or resource issues.

Mitigation

If you can’t patch tonight, do this now.

Until patches are applied, minimize exposure of the LON IP-852 management interface. Do not expose affected devices directly to the internet; restrict IP-852 traffic to trusted management networks using firewalls and ACLs; segment control networks from business networks; and use secure remote access such as updated VPNs rather than direct access. Monitor for anomalous or malformed IP-852 management traffic, especially unusual extended-header sizes or suspicious time-synchronization message patterns.

Remediation

Patch, then assume compromise.

Upgrade EnOcean SmartServer IoT to SmartServer 4.6 Update 2 (v4.60.023) or later, as EnOcean states this update addresses CVE-2026-22885. More generally, remediate by correcting the IP-852 extended-header parser so extndHdrSize and derived offsets are strictly validated against actual packet length and buffer boundaries before parsing or echoing payload data. Apply vendor fixes to any affected legacy i.LON devices if available.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
EnOceanSmartserver Iothardware

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity

Community discussion across Reddit, Mastodon, and other social sources.