Availability degradation via signed left shifts
Published Apr 21, 2026 · Updated Apr 21, 2026
Undefined behavior in BACnet Stack before 1.4.3 allows remote attackers to trigger invalid signed shifts via crafted APDU bytes. The decode_signed32() function in src/bacnet/bacint.c casts each APDU byte to int32_t before left-shifting it, so a high-bit byte produces an unrepresentable signed result. The effect requires a compiler build that turns this undefined behavior into incorrect code; no production miscompilation or direct exploit primitive is known.
Summary
What happened
Undefined behavior in BACnet Stack before 1.4.3 allows remote attackers to trigger invalid signed shifts via crafted APDU bytes. The decode_signed32() function in src/bacnet/bacint.c casts each APDU byte to int32_t before left-shifting it, so a high-bit byte produces an unrepresentable signed result. The effect requires a compiler build that turns this undefined behavior into incorrect code; no production miscompilation or direct exploit primitive is known.
The record
- CVE
- CVE-2026-40279
- Published
- Apr 21, 2026
- Updated
- Apr 21, 2026
- Vendor
- BACnet Stack
- Product
- BACnet Stack
- Classifications
- CWE-758
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 21, 2026CVE publishedPublication date reported by the CVE source.
- Apr 21, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.4.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
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
- decode_signed32 UBSan standalone reproducerproof of concept · demonstrated
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