Jovancoding
Network-AI
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 network-ai, 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-73615 | 13 Aug 2026 | < 5.15.1 | 5.15.1 | Update reference ↗ |
| CVE-2026-73614 | 13 Aug 2026 | < 5.15.1 | 5.15.1 | Update reference ↗ |
| CVE-2026-58484 | 20 Jul 2026 | < 5.12.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-58482 | 20 Jul 2026 | >= 5.0.0, < 5.12.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-46701 | 20 Jul 2026 | < 5.4.5 | 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-58481 | 20 Jul 2026 | < 5.12.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-58414 | 20 Jul 2026 | < 5.12.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-58413 | 20 Jul 2026 | < 5.12.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-54051 | 20 Jul 2026 | < 5.9.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-64623 | 20 Jul 2026 | < 5.13.4 | 5.13.4 | Update reference ↗ |
| CVE-2026-64622 | 20 Jul 2026 | 5.12.2 ≤ 5.13.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-48814 | 17 Jun 2026 | < 5.7.2 | 5.7.2. | Update reference ↗ |
| CVE-2026-42856 | 11 May 2026 | < 5.1.3 | 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.