SignalK
signalk-server
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
Official registry publication history is available at signalk-server, but registry activity is not a publisher support boundary.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-55591 | 15 Sep 2026 | signalk-server: < 2.28.0 | 2.28.0. | Update reference ↗ |
| CVE-2026-41893 | 9 May 2026 | < 2.25.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2026-39320 | 21 Apr 2026 | < 2.25.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2026-35038 | 2 Apr 2026 | < 2.24.0 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-34083 | 2 Apr 2026 | < 2.24.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-33951 | 2 Apr 2026 | < 2.24.0-beta.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-33950 | 2 Apr 2026 | < 2.24.0-beta.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-25228 | 2 Feb 2026 | < 2.20.3 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2026-23515 | 2 Feb 2026 | < 1.5.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2025-69203 | 1 Jan 2026 | signalk-server: < 2.19.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-68619 | 1 Jan 2026 | signalk-server: < 2.19.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-68620 | 1 Jan 2026 | signalk-server: < 2.19.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-68273 | 1 Jan 2026 | signalk-server: < 2.19.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-68272 | 1 Jan 2026 | signalk-server: < 2.19.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-66398 | 1 Jan 2026 | signalk-server: < 2.19.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.