Puppet
Puppet Enterprise
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
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
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2023-5309 | 7 Nov 2023 | 2021.7.0 < 2021.7.6; 2023.0.0 < 2023.5 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-5255 | 3 Oct 2023 | Puppet Enterprise 2023.3 ≤ 2023.4; Puppet Server 8.2.0 ≤ 8.2.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-2530 | 7 Jun 2023 | 2021.7.0 < 2021.7.4; 2023.0.0 < 2023.2.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-1894 | 4 May 2023 | 2021.7.1 < 2021.7.3; 2023.0.0 < 2023.1.0; 7.9.2 < 7.11.0; 7.9.2 < 8.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-11749 | 24 Aug 2018 | 2018.1.3; 2017.3.9; 2016.4.14 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-6511 | 8 May 2018 | 2017.3.x < 2017.3.6 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-6510 | 8 May 2018 | 2017.3.x < 2017.3.6 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-6508 | 9 Feb 2018 | 2017.3.x prior to 2017.3.4; prior to 0.1.5; prior to 4.5.1; prior to 5.2.1; prior to 2.3.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-10690 | 9 Feb 2018 | 2017.3.x prior to 2017.3.4; 5.x prior to 5.3.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-10689 | 9 Feb 2018 | prior to 2016.4.10 or 2017.3.4; prior to 5.3.4 or 1.10.10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-2297 | 1 Feb 2018 | 2016.4.x prior to 2016.4.5, 2016.5.x, 2017.1.x | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-2296 | 1 Feb 2018 | 2017.1.x, 2017.2.1. Fixed in 2017.2.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-2293 | 1 Feb 2018 | prior to 2016.4.5, 2016.5.x, 2017.1.x, resolved in 2016.4.5 and 2017.2.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2016-5716 | 9 Aug 2017 | PE < 2016.4.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-2294 | 5 Jul 2017 | PE prior to 2016.4.5 or 2017.2.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2016-9686 | 8 Feb 2017 | 2015.3.x; 2016.x prior to 2016.4.3; 2016.5.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.