CVE-2026-42804
HIGHDescription
A stack-based buffer overflow vulnerability exists in the Bosch Sensortec BHI360 SensorAPI(C-Library) in versions up to and including commit d6b200416a. The vulnerability is located within the FIFO parsing and debug logging subsystem inside the function bhi360_parse_debug_message() in bhi360_parse.c (lines 1852-1875). The parser trusts the first payload byte of a debug frame as the message length (msg_length) and copies that many bytes into a fixed-size 17-byte stack buffer (debug_msg) via memcpy without performing any bounds checking. A locally or physically positioned attacker (e.g., via a malicious sensor, counterfeit hardware module, or a Man-in-the-Middle on the communication bus) can exploit this vulnerability by injecting a crafted debug frame with a length byte exceeding 16. This corrupts adjacent stack data, including the saved return address. Furthermore, because the overflowed buffer is subsequently passed to a printf-style logging sink, the attacker can supply format string specifiers (e.g., %n) to execute arbitrary code on the host microcontroller/SoC or cause a reliable system crash (Denial of Service).
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 17% of all known CVEs.
References
Related Vulnerabilities
Other CWE-121 (Stack-based Buffer Overflow) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2025-22457 | Critical | 9.0 | 100% | KEV + Ransom | Fix |
| CVE-2025-0282 | Critical | 9.0 | 100% | KEV + Ransom | - |
| CVE-2021-20038 | Critical | 9.8 | 100% | KEV + Ransom | - |
| CVE-2009-0927 | High | 8.8 | 97% | KEV | Fix |
| CVE-2020-10924 | High | 8.8 | 87% | - | - |
| CVE-2022-20705 | Critical | 10.0 | 80% | - | - |
Common questions
How do I fix CVE-2026-42804?
No published fix for CVE-2026-42804 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-42804 being actively exploited?
Not that we know of. CVE-2026-42804 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.25% is the estimated probability that it will be exploited in the next 30 days. That is higher than 17% of all scored CVEs.
How severe is CVE-2026-42804?
CVE-2026-42804 has a CVSS v3 base score of 7.6, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-42804
Markdown
[](https://tridentstack.com/cve/CVE-2026-42804)HTML
<a href="https://tridentstack.com/cve/CVE-2026-42804"><img src="https://tridentstack.com/cve/badge/CVE-2026-42804.svg" alt="CVE-2026-42804"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-10.