Vulnerability · CVE-2025-55080
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.
Published Oct 15, 2025 · catalog updated Oct 15, 2025 · Eclipse Foundation ThreadX
Last checked Oct 26, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2025-55080. EPSS is 0.14%. Act only if a listed version of Eclipse Foundation ThreadX is installed.
Gaps on this record
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2025-55079 · Medium
- CVE-2025-55078 · Medium
- Severity
- High7.2
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.14%
- Remediation
- Version ranges on file
- Affected products
- vendor Eclipse Foundation ThreadX 0 <6.4.3
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.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- vendor Eclipse Foundation ThreadX 0 <6.4.30 <6.4.3
How to fix CVE-2025-55080
Upgrade
CVE-2025-55080 lists a fix boundary at 6.4.3. Compare the installed build with that boundary before you change production.
Version check
Seen in 0 <6.4.3
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2025-55080. EPSS is 0.14%. Act only if a listed version of Eclipse Foundation ThreadX is installed.
Which versions are affected?
Compare what you have installed with Eclipse Foundation ThreadX 0 <6.4.3 0 <6.4.3. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.14%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Oct 15, 2025 · EUVD
Detected
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.
Oct 15, 2025 · EUVD
Updated
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.
Sources
- CVE.orgVulnerability recordCVE-2025-55080
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2025-55080
30-day exploitation probability 0.14%
first.org - EUVDVulnerability recordEUVD-2025-34534
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.
euvd.enisa.europa.eu
References
Freshness
Last verified in this catalog Oct 26, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- EUVDOct 26, 2026
- CVE.orgOct 23, 2026
- FIRST EPSSOct 23, 2026