CVE-2026-75370: SpaceDot AcubeSAT OBC out-of-bounds read in MessageParser

CVE-2026-75370 · Severity: medium · CVSS 6.5 · Published 2026-08-24

SpaceDot AcubeSAT is an on-board computer system used in satellite operations to process commands and telemetry via CAN bus communication. A vulnerability in the message parsing component allows an attacker with adjacent network access to send a malformed command message that triggers reading of uninitialized memory and potential execution of arbitrary commands, disrupting satellite operations or causing data leakage.

Technologies: SpaceDot AcubeSAT OBC. Vendors: SpaceDot.

Quick answers

Is CVE-2026-75370 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-75370 being exploited in the wild.
How severe is CVE-2026-75370?
Medium severity, with a CVSS score of 6.5, published 24 August 2026.
Which products and versions are affected?
SpaceDot AcubeSAT OBC commit eaf90ec and likely prior versions.
Is there a fix for CVE-2026-75370?
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-75370 attacked?
It is attacked from the adjacent network, in device firmware.
Am I affected by CVE-2026-75370?
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 MessageParser::parseECSSTC function contains a hardcoded 64-byte length parameter when parsing ECSS PUS telecommand (TC) messages, regardless of the actual payload size received via CAN bus. The subsequent parseECSSTCHeader function uses std::copy to transfer 59 bytes (from offset 5 to 63) into a Message object without validating that the source buffer contains sufficient valid data. When a CAN message carries fewer than 64 bytes, the copy operation reads beyond the valid payload boundary, leaking residual data from the internal 1024-byte CAN buffer into the constructed TC message. An attacker with adjacent network access to the CAN bus can send a specially crafted TC message with undersized payload to trigger this out-of-bounds read. The leaked residual data may coincidentally form valid ECSS TC structures, leading to arbitrary telecommand execution, information disclosure, or denial of service. No patch information is publicly available.

Affected products

  • SpaceDot AcubeSAT OBC commit eaf90ec and likely prior versions

Timeline

  • 2026-08-05: disclosed: GitHub issue CVE-2026-75370 opened
  • 2026-08-24: advisory: Published on NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.