CVE-2026-38570
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 · uneditedbacnet_stack 1.3.1 contains an Out-of-bounds Read in bacnet_tag_number_decode which allows attackers to cause a denial of service.
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 · moderate confidenceAn out-of-bounds read vulnerability exists in the bacnet_tag_number_decode function of bacnet_stack version 1.3.1. The function decodes BACnet protocol tags without proper bounds checking, allowing attackers to read memory outside allocated buffers, which triggers denial of service.
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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify bacnet_stack installation locationSearch for bacnet_stack library files (libbacnet.so, libbacnet.a, or source directories) on the system using 'find / -name "*bacnet*" 2>/dev/null' or check project dependenciesAffected if bacnet_stack files are found and the version cannot be determined or shows 1.3.1
-
Determine installed bacnet_stack versionCheck the version string in library files, source code headers (version.h, config.h), or package manager output (dpkg -l, rpm -qi)Affected if Version resolves to 1.3.1 specifically
-
Locate the bacnet_tag_number_decode functionSearch source code for 'bacnet_tag_number_decode' function definition using 'grep -r "bacnet_tag_number_decode" .' in the source tree or examine symbols in compiled library with 'nm libbacnet.so | grep tag_number'Affected if The function exists in the codebase and the library version is 1.3.1
-
Verify BACnet protocol data processing is in useReview application code or configuration to confirm it processes BACnet protocol messages that would invoke the bacnet_tag_number_decode parsing functionAffected if Application decodes BACnet tags and the library version is 1.3.1
Environment is affected if bacnet_stack version 1.3.1 is deployed and the application processes BACnet protocol data using the vulnerable bacnet_tag_number_decode parsing function.
Generated from the published advisory. Verify against your own configuration.
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 dataApply bounds checking to the bacnet_tag_number_decode function to validate buffer limits before reading. If a patched version is available, upgrade to that version. Otherwise, implement proper input validation and boundary checks in the decode routine.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-38570 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-38570 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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