Cyber Resilience

CVE-2026-21870

Bacnetstack Bacnet Stack ≤ 1.4.2

Public PoC
Published
13 February 2026
Modified
18 February 2026
Patch / advisory
CVSS Score v3.1 5.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
EPSS Score 0.0024 15th percentile
Risk Priority 42 floored blend · peak EPSS

Summary

CVE-2026-21870 is a medium-severity Off-by-one Error (CWE-193) vulnerability in Bacnetstack Bacnet Stack. Its CVSS base score is 5.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 15th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

BACnet Protocol Stack library provides a BACnet application layer, network layer and media access (MAC) layer communications services. In 1.4.2, 1.5.0.rc2, and earlier, an off-by-one stack-based buffer overflow in the ubasic interpreter causes a crash (SIGABRT) when processing string literals…

more

longer than the buffer limit. The tokenizer_string function in src/bacnet/basic/program/ubasic/tokenizer.c incorrectly handles null termination for maximum-length strings. It writes a null byte to dest[40] when the buffer size is only 40 (indices 0-39), triggering a stack overflow.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-41502Same product: Bacnetstack Bacnet Stack
CVE-2025-66624Same product: Bacnetstack Bacnet Stack
CVE-2026-40279Same product: Bacnetstack Bacnet Stack
CVE-2026-26264Same product: Bacnetstack Bacnet Stack
CVE-2026-41503Same product: Bacnetstack Bacnet Stack
CVE-2026-41475Same product: Bacnetstack Bacnet Stack
CVE-2026-21878Same product: Bacnetstack Bacnet Stack
CVE-2023-51773Same product: Bacnetstack Bacnet Stack
CVE-2026-49127Shared CWE-193
CVE-2024-53149Shared CWE-193

Affected Assets

bacnetstack
bacnet stack
1.5.0 · ≤ 1.4.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V6.2.1

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover off-by-one errors in loops, bounds, and calculations before deployment.

Requiring documented development standards and tools can embed bounds-checking and arithmetic-correctness rules that stop off-by-one mistakes at introduction.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent off-by-one errors via reviews, static analysis, and testing.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development and acceptance can detect off-by-one errors before release.

prevents

Secure development life cycle includes requirements and reviews that can catch off-by-one errors.

prevents

Application security requirements can specify bounds-checking and input validation to prevent off-by-one errors.

prevents

Secure system architecture and engineering principles promote defensive coding practices that reduce off-by-one mistakes.

prevents

Secure coding directly addresses off-by-one errors through coding standards and peer review.

References