CVE-2025-55079

Missing check for thread priority

MEDIUM
5.5
CVSS Score
Published: October 15, 2025 at 04:29 AM UTC
Updated: October 8, 2026 at 12:10 PM UTC
1 product affected across 1 vendorThreadX

Using ThreadX by Eclipse Foundation?

Get instant alerts when new vulnerabilities affect ThreadX - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 6.4.30 ≤ v < 6.4.3*0
Affected range stops below 6.4.3, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (1)

Vendor AdvisoryExploitThird Party Advisory
Source: cverecord
https://github.com/eclipse-threadx/threadx/security/advisories/GHSA-w8rw-fqgj-9r49

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-770

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card