← Search results
CVE-LINKED INVENTORY136 SECURITY RECORDS
Jenkins project
Jenkins
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 jenkins, 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-84657 | 2 Sep 2026 | See the vendor and CVE records for the affected range. | Jenkins: 2.580 < *, 2.568.3 < 2.568.* | Update reference ↗ |
| CVE-2026-84656 | 2 Sep 2026 | See the vendor and CVE records for the affected range. | Jenkins: 2.580 < *, 2.568.3 < 2.568.* | Update reference ↗ |
| CVE-2026-84655 | 2 Sep 2026 | See the vendor and CVE records for the affected range. | Jenkins: 2.580 < *, 2.568.3 < 2.568.* | Update reference ↗ |
| CVE-2026-84654 | 2 Sep 2026 | See the vendor and CVE records for the affected range. | 2.580 < *; 2.568.3 < 2.568.* | Update reference ↗ |
| CVE-2026-84653 | 2 Sep 2026 | See the vendor and CVE records for the affected range. | Jenkins: 2.580 < *, < 2.421, 2.568.3 < 2.568.* | Update reference ↗ |
| CVE-2026-84652 | 2 Sep 2026 | See the vendor and CVE records for the affected range. | Jenkins: 2.580 < *, 2.568.3 < 2.568.* | Update reference ↗ |
| CVE-2026-84651 | 2 Sep 2026 | See the vendor and CVE records for the affected range. | Jenkins: 2.580 < *, 2.568.3 < 2.568.* | Update reference ↗ |
| CVE-2026-84650 | 2 Sep 2026 | See the vendor and CVE records for the affected range. | Jenkins: 2.580 < *, 2.568.3 < 2.568.* | Update reference ↗ |
| CVE-2026-84649 | 2 Sep 2026 | See the vendor and CVE records for the affected range. | Jenkins: 2.580 < *, < 2.447, 2.568.3 < 2.568.* | Update reference ↗ |
| CVE-2026-84648 | 2 Sep 2026 | See the vendor and CVE records for the affected range. | Jenkins: 2.580 < *, 2.568.3 < 2.568.* | Update reference ↗ |
| CVE-2026-84647 | 2 Sep 2026 | See the vendor and CVE records for the affected range. | Jenkins: 2.580 < *, 2.568.3 < 2.568.* | Update reference ↗ |
| CVE-2026-84646 | 2 Sep 2026 | See the vendor and CVE records for the affected range. | Jenkins: 2.580 < *, 2.568.3 < 2.568.* | Update reference ↗ |
| CVE-2026-84645 | 2 Sep 2026 | See the vendor and CVE records for the affected range. | Jenkins: 2.580 < *, 2.568.3 < 2.568.* | Update reference ↗ |
| CVE-2026-70430 | 5 Aug 2026 | See the vendor and CVE records for the affected range. | 2.576 < *; 2.568.2 < 2.568.* | Update reference ↗ |
| CVE-2026-70429 | 5 Aug 2026 | See the vendor and CVE records for the affected range. | 2.576 < *; 2.568.2 < 2.568.* | Update reference ↗ |
| CVE-2026-70428 | 5 Aug 2026 | See the vendor and CVE records for the affected range. | 2.576 < *; 2.568.2 < 2.568.* | Update reference ↗ |
| CVE-2026-70427 | 5 Aug 2026 | See the vendor and CVE records for the affected range. | 2.576 < *; 2.568.2 < 2.568.* | Update reference ↗ |
| CVE-2026-70426 | 5 Aug 2026 | See the vendor and CVE records for the affected range. | 2.576 < *; 2.568.2 < 2.568.*; 3385.vf1123fb_515da_ < *; 3355.3357.v931d3c992987 < 3355.* | Update reference ↗ |
| CVE-2026-53442 | 10 Jun 2026 | See the vendor and CVE records for the affected range. | 2.568 < *; 2.555.3 < 2.555.* | Update reference ↗ |
| CVE-2026-53441 | 10 Jun 2026 | See the vendor and CVE records for the affected range. | < 2.483; 2.568 < *; 2.555.3 < 2.555.* | Update reference ↗ |
| CVE-2026-53440 | 10 Jun 2026 | See the vendor and CVE records for the affected range. | 2.568 < *; 2.555.3 < 2.555.* | Update reference ↗ |
| CVE-2026-53439 | 10 Jun 2026 | See the vendor and CVE records for the affected range. | 2.568 < *; 2.555.3 < 2.555.* | Update reference ↗ |
| CVE-2026-53438 | 10 Jun 2026 | See the vendor and CVE records for the affected range. | 2.568 < *; 2.555.3 < 2.555.* | Update reference ↗ |
| CVE-2026-53437 | 10 Jun 2026 | See the vendor and CVE records for the affected range. | Jenkins: 2.568 < *, 2.555.3 < 2.555.* | Update reference ↗ |
| CVE-2026-53436 | 10 Jun 2026 | See the vendor and CVE records for the affected range. | 2.568 < *; 2.555.3 < 2.555.* | Update reference ↗ |
| CVE-2026-53435 | 10 Jun 2026 | See the vendor and CVE records for the affected range. | Jenkins: 2.568 < *, 2.555.3 < 2.555.* | Update reference ↗ |
| CVE-2026-33002 | 18 Mar 2026 | See the vendor and CVE records for the affected range. | < 2.426.3; 2.427 < 2.442; 2.555 < *; 2.541.3 < 2.541.* | Update reference ↗ |
| CVE-2026-33001 | 18 Mar 2026 | See the vendor and CVE records for the affected range. | Jenkins: 2.555 < *, 2.541.3 < 2.541.* | Update reference ↗ |
| CVE-2026-27100 | 18 Feb 2026 | See the vendor and CVE records for the affected range. | 2.551 < *; 2.541.2 < 2.541.* | Update reference ↗ |
| CVE-2026-27099 | 18 Feb 2026 | See the vendor and CVE records for the affected range. | < 2.483; 2.551 < *; 2.541.2 < 2.541.* | Update reference ↗ |
| CVE-2025-67639 | 10 Dec 2025 | See the vendor and CVE records for the affected range. | 2.541 < *; 2.528.3 < 2.528.* | Update reference ↗ |
| CVE-2025-67638 | 10 Dec 2025 | See the vendor and CVE records for the affected range. | 2.541 < *; 2.528.3 < 2.528.* | Update reference ↗ |
| CVE-2025-67637 | 10 Dec 2025 | See the vendor and CVE records for the affected range. | 2.541 < *; 2.528.3 < 2.528.* | Update reference ↗ |
| CVE-2025-67636 | 10 Dec 2025 | See the vendor and CVE records for the affected range. | 2.541 < *; 2.528.3 < 2.528.* | Update reference ↗ |
| CVE-2025-67635 | 10 Dec 2025 | See the vendor and CVE records for the affected range. | 2.541 < *; 2.528.3 < 2.528.* | Update reference ↗ |
| CVE-2025-59476 | 17 Sep 2025 | See the vendor and CVE records for the affected range. | 2.516.3 < 2.516.*; 2.528 < * | Update reference ↗ |
| CVE-2025-59475 | 17 Sep 2025 | See the vendor and CVE records for the affected range. | 2.516.3 < 2.516.*; 2.528 < * | Update reference ↗ |
| CVE-2025-59474 | 17 Sep 2025 | See the vendor and CVE records for the affected range. | < 2.387; 2.516.3 < 2.516.*; 2.528 < * | Update reference ↗ |
| CVE-2025-31721 | 2 Apr 2025 | See the vendor and CVE records for the affected range. | 2.492.3 < 2.492.*; 2.504 < * | Update reference ↗ |
| CVE-2025-31720 | 2 Apr 2025 | See the vendor and CVE records for the affected range. | 2.492.3 < 2.492.*; 2.504 < * | Update reference ↗ |
| CVE-2025-27625 | 5 Mar 2025 | See the vendor and CVE records for the affected range. | 2.492.2 < 2.492.*; 2.500 < * | Update reference ↗ |
| CVE-2025-27624 | 5 Mar 2025 | See the vendor and CVE records for the affected range. | 2.492.2 < 2.492.*; 2.500 < * | Update reference ↗ |
| CVE-2025-27623 | 5 Mar 2025 | See the vendor and CVE records for the affected range. | 2.492.2 < 2.492.*; 2.500 < * | Update reference ↗ |
| CVE-2025-27622 | 5 Mar 2025 | See the vendor and CVE records for the affected range. | 2.492.2 < 2.492.*; 2.500 < * | Update reference ↗ |
| CVE-2024-47804 | 2 Oct 2024 | See the vendor and CVE records for the affected range. | 2.462.3 < 2.462.*; 2.479 < * | Update reference ↗ |
| CVE-2024-47803 | 2 Oct 2024 | See the vendor and CVE records for the affected range. | 2.462.3 < 2.462.*; 2.479 < * | Update reference ↗ |
| CVE-2024-43045 | 7 Aug 2024 | See the vendor and CVE records for the affected range. | 2.452.4 < 2.452.*; 2.462.1 < 2.462.*; 2.471 < * | Update reference ↗ |
| CVE-2024-43044 | 7 Aug 2024 | See the vendor and CVE records for the affected range. | 2.452.4 < 2.452.*; 2.462.1 < 2.462.*; 2.471 < * | Update reference ↗ |
| CVE-2024-23898 | 24 Jan 2024 | See the vendor and CVE records for the affected range. | < 2.217; 2.442 < *; 2.426.3 < 2.426.*; 2.440.1 < 2.440.* | Update reference ↗ |
| CVE-2023-43498 | 20 Sep 2023 | See the vendor and CVE records for the affected range. | 2.424 < *; 2.414.2 < 2.414.* | 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.