{"schemaVersion":1,"url":"https://cve.openhack.com/cve/CVE-2026-62977","id":"CVE-2026-62977","title":"bacnet-stack data exposure in RAMFS FILE size changes","description":"BACnet Stack is a BACnet open source protocol stack C library for embedded systems. Prior to version 1.5.1, the BACnet FILE object implementation allows remote WriteProperty(PROP_FILE_SIZE) requests to change the size of a stream-access FILE object without checking whether that FILE is marked Read_Only. When the FILE backend is RAMFS, enlarging the file only performs realloc() and updates the stor","descriptionLong":"BACnet Stack is a BACnet open source protocol stack C library for embedded systems. Prior to version 1.5.1, the BACnet FILE object implementation allows remote WriteProperty(PROP_FILE_SIZE) requests to change the size of a stream-access FILE object without checking whether that FILE is marked Read_Only. When the FILE backend is RAMFS, enlarging the file only performs realloc() and updates the stored size; the newly exposed tail region is not initialized before later reads. As a result, a remote client can enlarge a read-only RAMFS-backed stream-access FILE and then immediately retrieve the newly exposed region with AtomicReadFile(stream-access). Depending on the allocator and build configuration, the returned data may contain sanitizer fill bytes, stale heap contents, or other unintended process memory. Shrinking the file through the same path can also remotely truncate content that was intended to be read-only. This issue has been patched in versions 1.5.1 and 1.6.0.","published":"2026-11-13T18:40:09.732Z","updated":"2026-11-19T20:45:35.325228897Z","reserved":"2026-07-14T22:48:09.780Z","status":"Undergoing Analysis","rejected":false,"assigner":"GitHub_M","metric":{"version":"4.0","score":6.9,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N","rating":"medium","source":"GitHub_M"},"metrics":[{"version":"4.0","score":6.9,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N","rating":"medium","source":"GitHub_M"},{"version":"4.0","score":6.9,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","rating":"medium","source":"github.com"},{"version":"4.0","score":null,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N","rating":"unrated","source":"OSV"}],"rating":"medium","products":["bacnet-stack"],"affectedProducts":[{"vendor":"bacnet-stack","product":"bacnet-stack","defaultStatus":null,"versions":[{"version":"< 1.5.1","status":"affected"}],"platforms":[]}],"packages":[],"cwes":["CWE-284","CWE-908"],"aliases":["GHSA-mwj7-2v5r-v934"],"references":[{"url":"https://github.com/bacnet-stack/bacnet-stack/security/advisories/GHSA-mwj7-2v5r-v934","tags":["x_refsource_CONFIRM","exploit","advisory"]},{"url":"https://github.com/bacnet-stack/bacnet-stack/pull/1411","tags":["x_refsource_MISC","fix"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/62xxx/CVE-2026-62977.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-62977","tags":["advisory"]}],"patchReferenced":true,"fixAvailable":true,"exploitReferenced":true,"kev":false,"kevAdded":null,"kevDue":null,"kevEntry":null,"ssvc":{"exploitation":"poc","automatable":"yes","technicalImpact":"partial"},"epss":0.00249,"epssPercentile":0.16411,"sources":[{"name":"CVE List","url":"https://www.cve.org/CVERecord?id=CVE-2026-62977","ok":true},{"name":"NVD","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-62977","ok":true,"note":"Undergoing Analysis"},{"name":"OSV","url":"https://osv.dev/vulnerability/CVE-2026-62977","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-62977","ok":true,"note":"scored 2026-11-19"}],"aiTitle":true,"tech":[],"critical":[],"attention":null}