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

decolua

9Router

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 9router, 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-103530 30 Sep 2026 9Router: 0.5.0, 0.5.1, 0.5.2, 0.5.3, 0.5.4, 0.5.5, 0.5.6, 0.5.7, 0.5.8, 0.5.9, 0.5.10, 0.5.11, 0.5.12, 0.5.13, 0.5.14, 0.5.15, 0.5.16, 0.5.17, 0.5.18, 0.5.19, 0.5.20, 0.5.21, 0.5.22, 0.5.23, 0.5.24, 0.5.25, 0.5.26, 0.5.27, 0.5.28, 0.5.29, 0.5.30, 0.5.31, 0.5.32, 0.5.33, 0.5.34, 0.5.35, 0.5.36, 0.5.37, 0.5.38, 0.5.39, 0.5.40, 0.5.41, 0.5.42, 0.5.43, 0.5.44, 0.5.45, 0.5.46, 0.5.47, 0.5.48, 0.5.49, 0.5.50, 0.5.51, 0.5.52, 0.5.53, 0.5.54, 0.5.55 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-56682 22 Sep 2026 9router: < 0.5.6 0.5.6. Update reference ↗
CVE-2026-56681 22 Sep 2026 9router: < 0.5.6 0.5.6. Update reference ↗
CVE-2026-72860 20 Aug 2026 9router: ≤ 0.5.55 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-56677 17 Aug 2026 9router: <= 0.5.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-63732 23 Jul 2026 < 0.4.60 0.4.60 Update reference ↗
CVE-2026-63313 23 Jul 2026 < 0.4.72 0.4.72 Update reference ↗
CVE-2026-62312 15 Jul 2026 < 0.5.2 0.5.2. Update reference ↗
CVE-2026-56678 15 Jul 2026 < 0.5.6 0.5.6. Update reference ↗
CVE-2026-56679 15 Jul 2026 < 0.5.4 0.5.4. Update reference ↗
CVE-2026-49353 15 Jul 2026 <= 0.4.45 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-49352 15 Jul 2026 >= 0.2.21, < 0.4.44 0.4.44 Update reference ↗
CVE-2026-46339 15 Jul 2026 >= 0.4.30, < 0.4.37 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-62328 13 Jul 2026 ≤ 0.4.41 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-62327 13 Jul 2026 ≤ 0.4.41 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-59801 13 Jul 2026 ≤ 0.4.41 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-56675 10 Jul 2026 < 0.5.2 0.5.2. Update reference ↗
CVE-2026-55638 10 Jul 2026 < 0.5.2 0.5.2. Update reference ↗
CVE-2026-55641 10 Jul 2026 < 0.5.2 0.5.2. Update reference ↗
CVE-2026-56676 10 Jul 2026 < 0.5.2 0.5.2. Update reference ↗
CVE-2026-55500 10 Jul 2026 < 0.4.80 0.4.80. Update reference ↗
CVE-2026-55501 10 Jul 2026 < 0.4.80 0.4.80. Update reference ↗
CVE-2026-59800 7 Jul 2026 < 0.4.44 0.4.44 Update reference ↗
CVE-2026-10269 1 Jun 2026 0.1; 0.2; 0.3; 0.4.0 0.4.1 Update reference ↗
CVE-2026-5842 9 Apr 2026 0.3.0; 0.3.1; 0.3.2; 0.3.3; 0.3.4; 0.3.5; 0.3.6; 0.3.7 0.3.75 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.