| Version | Supported |
|---|---|
| 0.9.x | Yes |
| Older | No, please update |
Please report privately and do not open a public issue. Use GitHub's private reporting: on the repository Security tab, choose "Report a vulnerability". Include the version, Windows build, steps to reproduce and the impact you see. This is a volunteer project; expect an acknowledgement but no guaranteed timeline.
- The backend, the Qt frontend, the
winlestiacommand and its named pipe (it is meant to be reachable only by the current user, with an allow-list of commands). - The installer and uninstaller, including the scheduled task, PATH entry and terminal integration.
- Handling of sensitive data: for example the Wi-Fi password path, logs, clipboard history.
- Anything that could leave a system without its taskbar, or that bypasses the restore paths.
- Supply-chain issues with what the installer downloads (Clink, pinned by SHA-256) or bundles.
- Weather: with no city set, the location is found from your IP address through wttr.in (which sees the address); the forecast comes from Open-Meteo.
- After uninstalling,
HKCU\Software\Winlestia\DisplayNameand%LOCALAPPDATA%\Panneauxare kept for later updates. Delete the folder and runRemove-Item -Path HKCU:\Software\Winlestia -Recurseto remove them.
- The binaries are not code-signed. SmartScreen warnings are expected. Users should verify the SHA-256 published with each release. A report that "the installer is unsigned" is not a vulnerability.
- Vulnerabilities in Windows, Qt, .NET or other third-party components themselves; report them upstream (tell us if Winlestia ships a vulnerable version).
- Issues requiring an attacker who already runs code as the same user with full access to their profile.
- Denial of service by deliberately overloading your own desktop.