CVE-2026-42804

HIGHPre-NVD 7.67.6—
EchelonGraph scoreHIGH confidence

Score 7.6 from GitHub Security Advisory (severity: HIGH) published 2026-09-10. A secondary CVSS source baseline 7.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.6EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.6Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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).

CVSS v3
7.6
EG Score
7.6HIGHhigh confidence
EG Risk
34
EG Risk 34/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity76% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
15th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 10, 2026

Last Modified

September 10, 2026

Advisory Details (1)

Auto-updated Sep 10, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-42804(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 26× in last 7d / 98× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-05 03:36 UTCEG score recompute
  2. 2026-10-05 03:36 UTCGHSA enrichment
  3. 2026-10-04 23:22 UTCEPSS rescore
  4. 2026-10-04 15:42 UTCGHSA enrichment
  5. 2026-10-04 03:48 UTCGHSA enrichment
  6. 2026-10-03 15:53 UTCEG score recompute
  7. 2026-10-03 15:53 UTCGHSA enrichment
  8. 2026-10-03 14:25 UTCEPSS rescore
  9. 2026-10-03 03:22 UTCEG score recompute
  10. 2026-10-03 03:22 UTCGHSA enrichment
  11. 2026-10-02 15:27 UTCGHSA enrichment
  12. 2026-10-02 03:28 UTCEG score recompute
  13. 2026-10-02 03:28 UTCGHSA enrichment
  14. 2026-10-01 19:50 UTCEPSS rescore
  15. 2026-10-01 14:37 UTCGHSA enrichment
  16. 2026-10-01 02:43 UTCEG score recompute
  17. 2026-10-01 02:43 UTCGHSA enrichment
  18. 2026-09-30 15:03 UTCEPSS rescore
  19. 2026-09-30 14:49 UTCGHSA enrichment
  20. 2026-09-30 02:46 UTCEG score recompute
  21. 2026-09-30 02:46 UTCGHSA enrichment
  22. 2026-09-29 14:52 UTCGHSA enrichment
  23. 2026-09-29 02:49 UTCEG score recompute
  24. 2026-09-29 02:49 UTCGHSA enrichment
  25. 2026-09-28 14:54 UTCEG score recompute
Show 73 more
  1. 2026-09-28 14:54 UTCGHSA enrichment
  2. 2026-09-28 02:59 UTCGHSA enrichment
  3. 2026-09-27 15:04 UTCEG score recompute
  4. 2026-09-27 15:03 UTCGHSA enrichment
  5. 2026-09-27 13:48 UTCEPSS rescore
  6. 2026-09-27 02:56 UTCEG score recompute
  7. 2026-09-27 02:56 UTCGHSA enrichment
  8. 2026-09-26 15:58 UTCEPSS rescore
  9. 2026-09-26 15:01 UTCGHSA enrichment
  10. 2026-09-26 02:05 UTCEG score recompute
  11. 2026-09-26 02:05 UTCGHSA enrichment
  12. 2026-09-25 14:10 UTCGHSA enrichment
  13. 2026-09-25 02:14 UTCGHSA enrichment
  14. 2026-09-24 14:19 UTCEG score recompute
  15. 2026-09-24 14:19 UTCGHSA enrichment
  16. 2026-09-24 01:56 UTCEG score recompute
  17. 2026-09-24 01:56 UTCGHSA enrichment
  18. 2026-09-23 17:53 UTCEPSS rescore
  19. 2026-09-23 14:02 UTCGHSA enrichment
  20. 2026-09-23 02:08 UTCEG score recompute
  21. 2026-09-23 02:08 UTCGHSA enrichment
  22. 2026-09-22 14:13 UTCGHSA enrichment
  23. 2026-09-22 02:19 UTCEG score recompute
  24. 2026-09-22 02:19 UTCGHSA enrichment
  25. 2026-09-21 14:24 UTCGHSA enrichment
  26. 2026-09-21 02:28 UTCEG score recompute
  27. 2026-09-21 02:28 UTCGHSA enrichment
  28. 2026-09-20 20:15 UTCEPSS rescore
  29. 2026-09-20 14:33 UTCGHSA enrichment
  30. 2026-09-20 02:38 UTCEG score recompute
  31. 2026-09-20 02:38 UTCGHSA enrichment
  32. 2026-09-19 14:44 UTCGHSA enrichment
  33. 2026-09-19 02:50 UTCEG score recompute
  34. 2026-09-19 02:50 UTCGHSA enrichment
  35. 2026-09-18 19:28 UTCEPSS rescore
  36. 2026-09-18 14:55 UTCGHSA enrichment
  37. 2026-09-18 03:01 UTCEG score recompute
  38. 2026-09-18 03:01 UTCGHSA enrichment
  39. 2026-09-17 19:31 UTCEPSS rescore
  40. 2026-09-17 15:07 UTCGHSA enrichment
  41. 2026-09-17 03:13 UTCGHSA enrichment
  42. 2026-09-16 15:18 UTCEG score recompute
  43. 2026-09-16 15:18 UTCGHSA enrichment
  44. 2026-09-16 14:08 UTCEPSS rescore
  45. 2026-09-16 05:15 UTCEPSS rescore
  46. 2026-09-16 03:23 UTCGHSA enrichment
  47. 2026-09-15 15:26 UTCGHSA enrichment
  48. 2026-09-15 03:30 UTCEG score recompute
  49. 2026-09-15 03:30 UTCGHSA enrichment
  50. 2026-09-14 15:36 UTCGHSA enrichment
  51. 2026-09-14 03:41 UTCEG score recompute
  52. 2026-09-14 03:41 UTCGHSA enrichment
  53. 2026-09-13 16:47 UTCEPSS rescore
  54. 2026-09-13 15:47 UTCGHSA enrichment
  55. 2026-09-13 03:53 UTCGHSA enrichment
  56. 2026-09-12 15:58 UTCEG score recompute
  57. 2026-09-12 15:58 UTCGHSA enrichment
  58. 2026-09-12 15:01 UTCEPSS rescore
  59. 2026-09-12 04:04 UTCGHSA enrichment
  60. 2026-09-11 16:10 UTCEG score recompute
  61. 2026-09-11 16:10 UTCGHSA enrichment
  62. 2026-09-11 14:53 UTCEPSS rescore
  63. 2026-09-11 09:37 UTCEPSS rescore
  64. 2026-09-11 04:15 UTCGHSA enrichment
  65. 2026-09-10 16:21 UTCGHSA enrichment
  66. 2026-09-10 15:58 UTCEG score recompute
  67. 2026-09-10 15:58 UTCGHSA enrichment
  68. 2026-09-10 15:22 UTCEG score recompute
  69. 2026-09-10 15:22 UTCGHSA enrichment
  70. 2026-09-10 09:36 UTCEG score recompute
  71. 2026-09-10 09:36 UTCGHSA enrichment
  72. 2026-09-10 09:02 UTCEG score recompute
  73. 2026-09-10 08:59 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-42804?
CVE-2026-42804 is a high vulnerability published on September 10, 2026. 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 bhi360parsedebugmessage() in bhi360parse.c…
When was CVE-2026-42804 disclosed?
CVE-2026-42804 was first published on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42804 actively exploited?
CVE-2026-42804 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (15th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-42804?
CVE-2026-42804 has a CVSS base score of 7.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-42804?
No fix for CVE-2026-42804 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-42804 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-42804

Explore →

Is Your Infrastructure Affected by CVE-2026-42804?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.