This Eclipse Foundation Project adheres to the Eclipse Foundation Vulnerability Reporting Policy.
If you think you have found a vulnerability in this repository, please report it to us through coordinated disclosure.
Please do not report security vulnerabilities through public issues, discussions, or change requests.
Instead, report it privately here on GitHub
You can find more information about reporting and disclosure at the Eclipse Foundation Security page.
Please include as much of the information listed below as you can to help us better understand and resolve the issue:
- The type of issue (e.g., buffer overflow, SQL injection, or cross-site scripting)
- Affected version(s)
- Impact of the issue, including how an attacker might exploit the issue
- Step-by-step instructions to reproduce the issue
- The location of the affected source code (tag/branch/commit or direct URL)
- Full paths of source file(s) related to the manifestation of the issue
- Configuration required to reproduce the issue
- Log files that are related to this issue (if possible)
- Proof-of-concept or exploit code (if possible)
This information will help us triage your report more quickly.
| Version | Supported |
|---|---|
| 6.5.x | ✅ |
Eclipse ThreadX publishes a release every quarter. There are no long-term support branches or backports to older releases.
Normally, fixes for non-critical vulnerabilities will ship in a regularly scheduled quarterly release. If fixes for an urgent or critical vulnerability must ship quickly, then the project will publish a hotfix release of the affected component(s) without waiting for the next quarterly release.
You can learn more about the project's release cadence in this blog post.