CVE-2025-55080: In Eclipse ThreadX before 6.4.3, when memory protection is enabled, syscall parameters verification wasn't enough…
CVE-2025-55080 · Severity: high · CVSS 7.1 · Published 2025-10-15
In Eclipse ThreadX before 6.4.3, when memory protection is enabled, syscall parameters verification wasn't enough, allowing an attacker to obtain an arbitrary memory read/write.
No. Junglewise Threat Intelligence has no report of CVE-2025-55080 being exploited in the wild.
How severe is CVE-2025-55080?
High severity, with a CVSS score of 7.1, published 15 October 2025.
Which products and versions are affected?
Eclipse ThreadX. The advisory does not name versions.
Is there a fix for CVE-2025-55080?
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.
Am I affected by CVE-2025-55080?
Check whether you run Eclipse ThreadX. 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.