Red Hat, Inc.
Openshift
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This CVE identity is linked to the Lifecycle record Red Hat OpenShift. Use that record for publisher support phases and retirement dates.
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-2019-19355 | 18 Mar 2020 | Openshift 4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-19351 | 18 Mar 2020 | Openshift 4 and 3.11 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-10213 | 25 Nov 2019 | versions Red Hat OpenShift 4.1 and Red Hat OpenShift 4.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-2019-14845 | 8 Oct 2019 | opneshift build 4.1 up to 4.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-10165 | 30 Jul 2019 | fixed in 4.1.3 | 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-2016-7075 | 10 Sep 2018 | n/a | 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-2017-12195 | 27 Jul 2018 | all | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-7534 | 11 Apr 2018 | 3.x | 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.