Xuxueli
xxl-job
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 xxl-job, 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-94426 | 21 Sep 2026 | xxl-job: 3.0, 3.1, 3.2, 3.3, 3.4, 3.5.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-94145 | 21 Sep 2026 | xxl-job: 3.0, 3.1, 3.2, 3.3, 3.4, 3.4.0, 3.4.1, 3.4.2, 3.5.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-90489 | 12 Sep 2026 | xxl-job: 3.0, 3.1, 3.2, 3.3, 3.4, 3.5.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-90488 | 12 Sep 2026 | xxl-job: 3.4.0, 3.4.1, 3.4.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-90487 | 12 Sep 2026 | xxl-job: 3.4.0, 3.4.1, 3.4.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-65316 | 21 Jul 2026 | xxl-job: ≤ 2.4.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-7306 | 28 Apr 2026 | 3.3.0; 3.3.1; 3.3.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-7305 | 28 Apr 2026 | 3.3.0; 3.3.1; 3.3.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-7303 | 28 Apr 2026 | 3.3.0; 3.3.1; 3.3.2 | 3.4.0 | Update reference ↗ |
| CVE-2026-3733 | 8 Mar 2026 | 3.3.0; 3.3.1; 3.3.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-9264 | 20 Aug 2025 | 3.1.0; 3.1.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-9263 | 20 Aug 2025 | 3.1.0; 3.1.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-7789 | 18 Jul 2025 | 3.1.0; 3.1.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-7788 | 18 Jul 2025 | 3.1.0; 3.1.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-7787 | 18 Jul 2025 | 3.1.0; 3.1.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-3366 | 6 Apr 2024 | 2.4.0; 2.4.1 | 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.