Service crash via negative signed left shift
Published Sep 24, 2026 · Updated Sep 24, 2026
Undefined behavior in ZBar at commit 2ea2ca58 allows context-dependent attackers to crash trap-mode builds via crafted Code 128 input. In decode6(), decode_e() can return -1 for an invalid edge pattern, and the function left-shifts that negative signed value while assembling the edge signature. The service interruption requires a specially crafted barcode to reach the Code 128 decoder and is documented as SIGILL termination under trap-mode UBSan.
Summary
What happened
Undefined behavior in ZBar at commit 2ea2ca58 allows context-dependent attackers to crash trap-mode builds via crafted Code 128 input. In decode6(), decode_e() can return -1 for an invalid edge pattern, and the function left-shifts that negative signed value while assembling the edge signature. The service interruption requires a specially crafted barcode to reach the Code 128 decoder and is documented as SIGILL termination under trap-mode UBSan.
The record
- CVE
- CVE-2026-88371
- Published
- Sep 24, 2026
- Updated
- Sep 24, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1499.004
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 24, 2026CVE publishedPublication date reported by the CVE source.
- Sep 24, 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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started