Quick answers
- Is CVE-2026-75371 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-75371 being exploited in the wild.
- How severe is CVE-2026-75371?
- High severity, with a CVSS score of 7.5, published 24 August 2026.
- Which products and versions are affected?
- SpaceDot AcubeSAT OBC commit eaf90ec.
- Is there a fix for CVE-2026-75371?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-75371 attacked?
- It is attacked with physical access, in device firmware.
- Am I affected by CVE-2026-75371?
- Check whether you run SpaceDot AcubeSAT OBC at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a combination of two integer handling flaws (CWE-190, CWE-197, CWE-119) in the cobs_decode function: (1) signed vs. unsigned comparison of pointer differences against unsigned integers, which can bypass buffer boundary checks if pointers are corrupted; (2) 8-bit truncation of 32-bit pointer differences when checking remaining buffer space, discarding upper 24 bits and miscalculating available space. Attack vector is physical: an attacker must connect directly to the USART serial interface and send a malformed COBS-encoded message with invalid control bytes or length fields that exceed remaining data. In the current implementation using 128-byte buffers, exploitability is limited to message rejection and single-message DoS; the truncation flaw is theoretical and not triggered in practice. No patch status is currently documented.
Affected products
- SpaceDot AcubeSAT OBC commit eaf90ec
Timeline
- 2026-08-24: disclosed
- 2026-08-05: other: vulnerability reported to GitHub issue