Skip to content

Updated security policy #80

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
fdesbiens merged 1 commit into from
Jun 30, 2026
Merged

Updated security policy #80

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
39 changes: 29 additions & 10 deletions SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,20 +1,39 @@
# Security Policy

## Supported Versions
This Eclipse Foundation Project adheres to the [Eclipse Foundation Vulnerability Reporting Policy](https://www.eclipse.org/security/policy/).

| Version | Supported |
| ------- | ------------------ |
| 6.4.x | :white_check_mark: |
## How To Report a Vulnerability

## Reporting a Vulnerability
If you think you have found a vulnerability in this repository, please report it to us through coordinated disclosure.

If you think you have found a vulnerability in <project> you can report it using one of the following ways:
**Please do not report security vulnerabilities through public issues, discussions, or change requests.**

* Contact the [Eclipse Foundation Security Team](mailto:security@eclipse-foundation.org)
* [Report a Vulnerability](https://github.com/eclipse-threadx/levelx/security/advisories/new)
Instead, [report it privately here](https://github.com/eclipse-threadx/levelx/security/advisories/new) on GitHub

You can find more information about reporting and disclosure at the [Eclipse Foundation Security page](https://www.eclipse.org/security/).

## Security Policy
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.

## Supported Versions

| Version | Supported |
| ------- | ------------------ |
| 6.5.x | :white_check_mark: |

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.

This project follows [Eclipse Foundation Vulnerability Reporting Policy](https://www.eclipse.org/security/policy/).
You can learn more about the [project's release cadence in this blog post](https://blogs.eclipse.org/post/fr%C3%A9d%C3%A9ric-desbiens/eclipse-threadx-more-predictable-more-open).
Loading