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

jeecgboot

jimureport

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

Lifecycle evidence status

This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.

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-75479 17 Aug 2026 jimureport: ≤ 2.3.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-58375 30 Jun 2026 ≤ 2.5.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-5848 9 Apr 2026 2.0; 2.1; 2.2; 2.3.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-10771 21 Sep 2025 2.1.0; 2.1.1; 2.1.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-10770 21 Sep 2025 2.1.0; 2.1.1; 2.1.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-8963 14 Aug 2025 2.1.0; 2.1.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-6307 27 Nov 2023 1.6.0; 1.6.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-4450 21 Aug 2023 1.0; 1.1; 1.2; 1.3; 1.4; 1.5; 1.6 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.