Application crash from out-of-bounds read
Published Jun 4, 2026 · Updated Jun 4, 2026
Out-of-bounds read in BACnet Stack 1.3.1 allows attackers to crash the processing application via unspecified vectors. The published record identifies bacnet_tag_number_decode as the faulting locus but does not disclose the malformed input or incorrect operation that causes the invalid read. Required privileges, network position, and the reachable BACnet service path are not published, so the documented consequence is bounded to a service interrupt in the embedding application.
Summary
What happened
Out-of-bounds read in BACnet Stack 1.3.1 allows attackers to crash the processing application via unspecified vectors. The published record identifies bacnet_tag_number_decode as the faulting locus but does not disclose the malformed input or incorrect operation that causes the invalid read. Required privileges, network position, and the reachable BACnet service path are not published, so the documented consequence is bounded to a service interrupt in the embedding application.
The record
- CVE
- CVE-2026-38570
- Published
- Jun 4, 2026
- Updated
- Jun 4, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1499.004
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Jun 4, 2026CVE publishedPublication date reported by the CVE source.
- Jun 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo