Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY7 SECURITY RECORDS

sveltejs

devalue

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

Official registry publication history is available at devalue, 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

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2026-92708 18 Sep 2026 devalue: >= 5.1.0, < 5.9.3 5.9.3. Update reference ↗
CVE-2026-81176 16 Sep 2026 devalue: < 5.9.2 5.9.2. Update reference ↗
CVE-2026-42570 9 Jun 2026 >= 5.6.3, < 5.8.1 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Update reference ↗
CVE-2026-30226 11 Mar 2026 < 5.6.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-22775 15 Jan 2026 >= 5.1.0, < 5.6.2 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-22774 15 Jan 2026 >= 5.3.0, < 5.6.2 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-57820 26 Aug 2025 < 5.3.2 5.3.2 Update reference ↗

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.