{"schemaVersion":1,"url":"https://cve.openhack.com/cve/CVE-2026-52786","id":"CVE-2026-52786","title":"bacnet-stack EPICS client storage overflow in ReadPropertyMultiple ACK handling","description":"BACnet Stack is a BACnet open source protocol stack C library for embedded systems. Prior to versions 1.4.5, 1.5.1, and 1.6.0, in the official apps/epics client tool on v1.6.0-rc1 (not in the generic BACnet RPM ACK decoder alone) a malicious BACnet/IP endpoint can reply to the EPICS tool’s legitimate ReadPropertyMultiple request with a syntactically valid ReadPropertyMultiple-ACK that contains mor","descriptionLong":"BACnet Stack is a BACnet open source protocol stack C library for embedded systems. Prior to versions 1.4.5, 1.5.1, and 1.6.0, in the official apps/epics client tool on v1.6.0-rc1 (not in the generic BACnet RPM ACK decoder alone) a malicious BACnet/IP endpoint can reply to the EPICS tool’s legitimate ReadPropertyMultiple request with a syntactically valid ReadPropertyMultiple-ACK that contains more heading properties than the tool’s fixed local storage can hold. The response is decoded successfully and later consumed by ProcessRPMData(), which writes property values into a fixed global array using an unbounded linear index. This results in a reproducible global-buffer-overflow in apps/epics/main.c. This is a network-reachable memory corruption in the official epics tool’s response-processing path. The root cause is that apps/epics treats a remotely supplied variable-length RPM property list as if it were a trusted, fixed-size local heading-property set. This issue has been patched in versions 1.4.5, 1.5.1, and 1.6.0.","published":"2026-11-12T19:59:45.264Z","updated":"2026-11-17T20:45:50.672061481Z","reserved":"2026-06-08T18:02:19.730Z","status":"Undergoing Analysis","rejected":false,"assigner":"GitHub_M","metric":{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H","rating":"high","source":"GitHub_M"},"metrics":[{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H","rating":"high","source":"GitHub_M"},{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H","rating":"high","source":"github.com"},{"version":"3.1","score":7.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H","rating":"high","source":"OSV"}],"rating":"high","products":["bacnet-stack"],"affectedProducts":[{"vendor":"bacnet-stack","product":"bacnet-stack","defaultStatus":null,"versions":[{"version":"< 1.4.5","status":"affected"},{"version":"< 1.5.1","status":"affected"},{"version":"< 1.6.0","status":"affected"}],"platforms":[]}],"packages":[],"cwes":["CWE-129","CWE-787"],"aliases":["GHSA-c4q6-7827-mfg6"],"references":[{"url":"https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-c4q6-7827-mfg6","tags":["x_refsource_CONFIRM","exploit","advisory"]},{"url":"https://github.com/bacnet-stack/bacnet-stack/pull/1366","tags":["x_refsource_MISC","fix"]},{"url":"https://github.com/bacnet-stack/bacnet-stack/pull/1409","tags":["x_refsource_MISC","fix"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/52xxx/CVE-2026-52786.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-52786","tags":["advisory"]}],"patchReferenced":true,"fixAvailable":true,"exploitReferenced":true,"kev":false,"kevAdded":null,"kevDue":null,"kevEntry":null,"ssvc":{"exploitation":"poc","automatable":"no","technicalImpact":"partial"},"epss":0.0022,"epssPercentile":0.12635,"sources":[{"name":"CVE List","url":"https://www.cve.org/CVERecord?id=CVE-2026-52786","ok":true},{"name":"NVD","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-52786","ok":true,"note":"Undergoing Analysis"},{"name":"OSV","url":"https://osv.dev/vulnerability/CVE-2026-52786","ok":true,"note":"0 packages"},{"name":"CISA KEV","url":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","ok":true,"note":"not listed"},{"name":"EPSS","url":"https://api.first.org/data/v1/epss?cve=CVE-2026-52786","ok":true,"note":"scored 2026-11-19"}],"aiTitle":true,"tech":[],"critical":[],"attention":"Public exploit referenced within two weeks of publication"}