← Search results
CVE-LINKED INVENTORY83 SECURITY RECORDS
ISC
BIND 9
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-2026-77119 | 16 Sep 2026 | BIND 9: 9.11.0 ≤ 9.18.50, 9.20.0 ≤ 9.20.27, 9.21.0 ≤ 9.21.25, 9.11.3-S1 ≤ 9.18.50-S1, 9.20.9-S1 ≤ 9.20.27-S1 | Upgrade to the patched release most closely related to your current version of BIND 9: 9.20.29, 9.21.26, or 9.20.29-S1. | Update reference ↗ |
| CVE-2026-75029 | 16 Sep 2026 | BIND 9: 9.11.0 ≤ 9.18.50, 9.20.0 ≤ 9.20.27, 9.21.0 ≤ 9.21.25, 9.11.3-S1 ≤ 9.18.50-S1, 9.20.9-S1 ≤ 9.20.27-S1 | Upgrade to the patched release most closely related to your current version of BIND 9: 9.20.29, 9.21.26, or 9.20.29-S1. | Update reference ↗ |
| CVE-2026-19668 | 16 Sep 2026 | BIND 9: 9.11.0 ≤ 9.18.50, 9.20.0 ≤ 9.20.27, 9.21.0 ≤ 9.21.25, 9.11.3-S1 ≤ 9.18.50-S1, 9.20.9-S1 ≤ 9.20.27-S1 | Upgrade to the patched release most closely related to your current version of BIND 9: 9.20.29, 9.21.26, or 9.20.29-S1. | Update reference ↗ |
| CVE-2026-19033 | 16 Sep 2026 | BIND 9: 9.11.0 ≤ 9.18.50, 9.20.0 ≤ 9.20.27, 9.21.0 ≤ 9.21.25, 9.11.3-S1 ≤ 9.18.50-S1, 9.20.9-S1 ≤ 9.20.27-S1 | Upgrade to the patched release most closely related to your current version of BIND 9: 9.20.29, 9.21.26, or 9.20.29-S1. | Update reference ↗ |
| CVE-2026-80274 | 16 Sep 2026 | BIND 9: 9.11.0 ≤ 9.18.50, 9.20.0 ≤ 9.20.27, 9.21.0 ≤ 9.21.25, 9.11.3-S1 ≤ 9.18.50-S1, 9.20.9-S1 ≤ 9.20.27-S1 | Upgrade to the patched release most closely related to your current version of BIND 9: 9.20.29, 9.21.26, or 9.20.29-S1. | Update reference ↗ |
| CVE-2026-76163 | 16 Sep 2026 | BIND 9: 9.20.0 ≤ 9.20.27, 9.21.0 ≤ 9.21.25, 9.20.9-S1 ≤ 9.20.27-S1 | Upgrade to the patched release most closely related to your current version of BIND 9: 9.20.29, 9.21.26, or 9.20.29-S1. | Update reference ↗ |
| CVE-2026-19666 | 16 Sep 2026 | BIND 9: 9.11.0 ≤ 9.18.50, 9.20.0 ≤ 9.20.27, 9.21.0 ≤ 9.21.25, 9.11.3-S1 ≤ 9.18.50-S1, 9.20.9-S1 ≤ 9.20.27-S1 | Upgrade to the patched release most closely related to your current version of BIND 9: 9.20.29, 9.21.26, or 9.20.29-S1. | Update reference ↗ |
| CVE-2026-81563 | 16 Sep 2026 | BIND 9: 9.18.0 ≤ 9.18.50, 9.20.0 ≤ 9.20.27, 9.21.0 ≤ 9.21.25, 9.18.11-S1 ≤ 9.18.50-S1, 9.20.9-S1 ≤ 9.20.27-S1 | Upgrade to the patched release most closely related to your current version of BIND 9: 9.20.29, 9.21.26, or 9.20.29-S1. | Update reference ↗ |
| CVE-2026-78301 | 16 Sep 2026 | BIND 9: 9.11.0 ≤ 9.18.50, 9.20.0 ≤ 9.20.27, 9.21.0 ≤ 9.21.25, 9.11.3-S1 ≤ 9.18.50-S1, 9.20.9-S1 ≤ 9.20.27-S1 | Upgrade to the patched release most closely related to your current version of BIND 9: 9.20.29, 9.21.26, or 9.20.29-S1. | Update reference ↗ |
| CVE-2026-77692 | 16 Sep 2026 | BIND 9: 9.20.0 ≤ 9.20.27, 9.21.0 ≤ 9.21.25, 9.20.9-S1 ≤ 9.20.27-S1 | Upgrade to the patched release most closely related to your current version of BIND 9: 9.20.29, 9.21.26, or 9.20.29-S1. | Update reference ↗ |
| CVE-2026-19941 | 16 Sep 2026 | BIND 9: 9.11.0 ≤ 9.18.50, 9.20.0 ≤ 9.20.27, 9.21.0 ≤ 9.21.25, 9.11.3-S1 ≤ 9.18.50-S1, 9.20.9-S1 ≤ 9.20.27-S1 | Upgrade to the patched release most closely related to your current version of BIND 9: 9.20.29, 9.21.26, or 9.20.29-S1. | Update reference ↗ |
| CVE-2026-19662 | 16 Sep 2026 | BIND 9: 9.11.0 ≤ 9.18.50, 9.20.0 ≤ 9.20.27, 9.11.3-S1 ≤ 9.18.50-S1, 9.20.9-S1 ≤ 9.20.27-S1 | Upgrade to the patched release most closely related to your current version of BIND 9: 9.20.29 or 9.20.29-S1. | Update reference ↗ |
| CVE-2026-19667 | 16 Sep 2026 | BIND 9: 9.11.0 ≤ 9.18.50, 9.20.0 ≤ 9.20.27, 9.21.0 ≤ 9.21.25, 9.11.3-S1 ≤ 9.18.50-S1, 9.20.9-S1 ≤ 9.20.27-S1 | Upgrade to the patched release most closely related to your current version of BIND 9: 9.20.29, 9.21.26, or 9.20.29-S1. | Update reference ↗ |
| CVE-2026-81736 | 16 Sep 2026 | BIND 9: 9.18.0 ≤ 9.18.50, 9.20.0 ≤ 9.20.27, 9.21.0 ≤ 9.21.25, 9.18.11-S1 ≤ 9.18.50-S1, 9.20.9-S1 ≤ 9.20.27-S1 | Upgrade to the patched release most closely related to your current version of BIND 9: 9.20.29, 9.21.26, or 9.20.29-S1. | Update reference ↗ |
| CVE-2026-13321 | 22 Jul 2026 | 9.11.0 ≤ 9.18.50; 9.20.0 ≤ 9.20.24; 9.21.0 ≤ 9.21.23; 9.11.3-S1 ≤ 9.18.50-S1; 9.20.9-S1 ≤ 9.20.24-S1 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-13204 | 22 Jul 2026 | 9.11.0 ≤ 9.18.50; 9.20.0 ≤ 9.20.24; 9.21.0 ≤ 9.21.23; 9.11.3-S1 ≤ 9.18.50-S1; 9.20.9-S1 ≤ 9.20.24-S1 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-12617 | 22 Jul 2026 | 9.18.0 ≤ 9.18.50; 9.20.0 ≤ 9.20.24; 9.18.11-S1 ≤ 9.18.50-S1; 9.20.9-S1 ≤ 9.20.24-S1 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ | Update reference ↗ |
| CVE-2026-11721 | 22 Jul 2026 | 9.11.0 ≤ 9.18.50; 9.20.0 ≤ 9.20.24; 9.21.0 ≤ 9.21.23; 9.11.3-S1 ≤ 9.18.50-S1; 9.20.9-S1 ≤ 9.20.24-S1 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-11622 | 22 Jul 2026 | 9.11.0 ≤ 9.18.50; 9.20.0 ≤ 9.20.24; 9.21.0 ≤ 9.21.23; 9.11.3-S1 ≤ 9.18.50-S1; 9.20.9-S1 ≤ 9.20.24-S1 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-11605 | 22 Jul 2026 | 9.20.0 ≤ 9.20.24; 9.21.0 ≤ 9.21.23; 9.20.9-S1 ≤ 9.20.24-S1 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ | Update reference ↗ |
| CVE-2026-11331 | 22 Jul 2026 | 9.16.0 ≤ 9.18.50; 9.20.0 ≤ 9.20.24; 9.21.0 ≤ 9.21.23; 9.16.8-S1 ≤ 9.18.50-S1; 9.20.9-S1 ≤ 9.20.24-S1 | For OpenShift Container Platform 4.16 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.16/html/release_notes/ You may download the oc tool and use it to inspect release image metadata for x86_64, s390x, ppc64le, and aarch64 architectures. The image digests may be found at https://quay.io/repository/openshift-release-dev/ocp-release?tab=tags. The sha values for the release are as follows: (For x86_64 architecture) The image digest is sha256:077bb2d0f053cfadc673374237b206740ab78f2663d3dbd1b49713c2ced88994 (For s390x architecture) The image digest is sha256:a46bf8cdae866571521a66b6efa1634db5109b020ab9ed6d8de1caf815bfe25a (For ppc64le architecture) The image digest is sha256:6e0b33f7d8db91651807aabffce25e1cdf27f90a6240ac49bd651c64b05464c3 (For aarch64 architecture) The image digest is sha256:e76b87d63f7b8b2960353d5cc3e7bf427b65edd8e95c8c51fbb7c12a6ea4fb34 All OpenShift Container Platform 4.16 users are advised to upgrade to these updated packages and images when they are available in the appropriate release channel. To check for available updates, use the OpenShift CLI (oc) or web console. Instructions for upgrading a cluster are available at https://docs.redhat.com/en/documentation/openshift_container_platform/4.16/html-single/updating_clusters/index#updating-cluster-cli. | Update reference ↗ |
| CVE-2026-10822 | 22 Jul 2026 | 9.18.0 ≤ 9.18.50; 9.20.0 ≤ 9.20.24; 9.21.0 ≤ 9.21.23; 9.18.11-S1 ≤ 9.18.50-S1; 9.20.9-S1 ≤ 9.20.24-S1 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ | Update reference ↗ |
| CVE-2026-10723 | 22 Jul 2026 | 9.18.0 ≤ 9.18.50; 9.20.0 ≤ 9.20.24; 9.21.0 ≤ 9.21.23; 9.11.3-S1 ≤ 9.18.50-S1; 9.20.9-S1 ≤ 9.20.24-S1 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-5950 | 20 May 2026 | 9.18.36 ≤ 9.18.48; 9.20.8 ≤ 9.20.22; 9.21.7 ≤ 9.21.21; 9.18.36-S1 ≤ 9.18.48-S1; 9.20.9-S1 ≤ 9.20.22-S1 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ | Update reference ↗ |
| CVE-2026-5947 | 20 May 2026 | BIND 9: 9.20.0 ≤ 9.20.22, 9.21.0 ≤ 9.21.21, 9.20.9-S1 ≤ 9.20.22-S1 | BIND 9: 9.18.28 ≤ 9.18.49, 9.18.28-S1 ≤ 9.18.49-S1 | Update reference ↗ |
| CVE-2026-5946 | 20 May 2026 | BIND 9: 9.11.0 ≤ 9.16.50, 9.18.0 ≤ 9.18.48, 9.20.0 ≤ 9.20.22, 9.21.0 ≤ 9.21.21, 9.11.3-S1 ≤ 9.16.50-S1, 9.18.11-S1 ≤ 9.18.48-S1, 9.20.9-S1 ≤ 9.20.22-S1 | Upgrade to the patched release most closely related to your current version of BIND 9: 9.18.49, 9.20.23, 9.21.22, 9.18.49-S1, or 9.20.23-S1. | Update reference ↗ |
| CVE-2026-3593 | 20 May 2026 | BIND 9: 9.20.0 ≤ 9.20.22, 9.21.0 ≤ 9.21.21, 9.20.9-S1 ≤ 9.20.22-S1 | BIND 9: 9.18.0 ≤ 9.18.48, 9.18.11-S1 ≤ 9.18.48-S1 | Update reference ↗ |
| CVE-2026-3592 | 20 May 2026 | 9.11.0 ≤ 9.16.50; 9.18.0 ≤ 9.18.48; 9.20.0 ≤ 9.20.22; 9.21.0 ≤ 9.21.21; 9.11.3-S1 ≤ 9.16.50-S1; 9.18.11-S1 ≤ 9.18.48-S1; 9.20.9-S1 ≤ 9.20.22-S1 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ | Update reference ↗ |
| CVE-2026-3039 | 20 May 2026 | BIND 9: 9.0.0 ≤ 9.16.50, 9.18.0 ≤ 9.18.48, 9.20.0 ≤ 9.20.22, 9.21.0 ≤ 9.21.21, 9.9.3-S1 ≤ 9.16.50-S1, 9.18.11-S1 ≤ 9.18.48-S1, 9.20.9-S1 ≤ 9.20.22-S1 | Upgrade to the patched release most closely related to your current version of BIND 9: 9.18.49, 9.20.23, 9.21.22, 9.18.49-S1, or 9.20.23-S1. | Update reference ↗ |
| CVE-2026-3591 | 25 Mar 2026 | 9.20.0 ≤ 9.20.20; 9.21.0 ≤ 9.21.19; 9.20.9-S1 ≤ 9.20.20-S1 | 9.18.0 ≤ 9.18.46; 9.18.11-S1 ≤ 9.18.46-S1 | Update reference ↗ |
| CVE-2026-3119 | 25 Mar 2026 | 9.20.0 ≤ 9.20.20; 9.21.0 ≤ 9.21.19; 9.20.9-S1 ≤ 9.20.20-S1 | 9.18.0 ≤ 9.18.46; 9.18.11-S1 ≤ 9.18.46-S1 | Update reference ↗ |
| CVE-2026-3104 | 25 Mar 2026 | BIND 9: 9.20.0 ≤ 9.20.20, 9.21.0 ≤ 9.21.19, 9.20.9-S1 ≤ 9.20.20-S1 | BIND 9: 9.18.0 ≤ 9.18.46, 9.18.11-S1 ≤ 9.18.46-S1 | Update reference ↗ |
| CVE-2026-1519 | 25 Mar 2026 | BIND 9: 9.11.0 ≤ 9.16.50, 9.18.0 ≤ 9.18.46, 9.20.0 ≤ 9.20.20, 9.21.0 ≤ 9.21.19, 9.11.3-S1 ≤ 9.16.50-S1, 9.18.11-S1 ≤ 9.18.46-S1, 9.20.9-S1 ≤ 9.20.20-S1 | Upgrade to the patched release most closely related to your current version of BIND 9: 9.18.47, 9.20.21, 9.21.20, 9.18.47-S1, or 9.20.21-S1. | Update reference ↗ |
| CVE-2025-13878 | 21 Jan 2026 | BIND 9: 9.18.40 ≤ 9.18.43, 9.20.13 ≤ 9.20.17, 9.21.12 ≤ 9.21.16, 9.18.40-S1 ≤ 9.18.43-S1, 9.20.13-S1 ≤ 9.20.17-S1 | Upgrade to the patched release most closely related to your current version of BIND 9: 9.18.44, 9.20.18, 9.21.17, 9.18.44-S1, or 9.20.18-S1. | Update reference ↗ |
| CVE-2025-40780 | 22 Oct 2025 | 9.16.0 ≤ 9.16.50; 9.18.0 ≤ 9.18.39; 9.20.0 ≤ 9.20.13; 9.21.0 ≤ 9.21.12; 9.16.8-S1 ≤ 9.16.50-S1; 9.18.11-S1 ≤ 9.18.39-S1; 9.20.9-S1 ≤ 9.20.13-S1 | For OpenShift Container Platform 4.12 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.12/html/release_notes You may download the oc tool and use it to inspect release image metadata for the x86_64 architecture. The image digest may be found at https://quay.io/repository/openshift-release-dev/ocp-release?tab=tags. The sha value for the release is as follows: (For x86_64 architecture) The image digest is sha256:9ea794d2dd24ff7377534edfb0447e5398a28919a84300cc79fe7bb8ae550d1b All OpenShift Container Platform 4.12 users are advised to upgrade to these updated packages and images when they are available in the appropriate release channel. To check for available updates, use the OpenShift CLI (oc) or web console. Instructions for upgrading a cluster are available at https://docs.redhat.com/en/documentation/openshift_container_platform/4.12/html-single/updating_clusters/index#updating-cluster-within-minor. | Update reference ↗ |
| CVE-2025-40778 | 22 Oct 2025 | 9.11.0 ≤ 9.16.50; 9.18.0 ≤ 9.18.39; 9.20.0 ≤ 9.20.13; 9.21.0 ≤ 9.21.12; 9.11.3-S1 ≤ 9.16.50-S1; 9.18.11-S1 ≤ 9.18.39-S1; 9.20.9-S1 ≤ 9.20.13-S1 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2025-8677 | 22 Oct 2025 | 9.18.0 ≤ 9.18.39; 9.20.0 ≤ 9.20.13; 9.21.0 ≤ 9.21.12; 9.18.11-S1 ≤ 9.18.39-S1; 9.20.9-S1 ≤ 9.20.13-S1 | For OpenShift Container Platform 4.12 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.12/html/release_notes You may download the oc tool and use it to inspect release image metadata for the x86_64 architecture. The image digest may be found at https://quay.io/repository/openshift-release-dev/ocp-release?tab=tags. The sha value for the release is as follows: (For x86_64 architecture) The image digest is sha256:9ea794d2dd24ff7377534edfb0447e5398a28919a84300cc79fe7bb8ae550d1b All OpenShift Container Platform 4.12 users are advised to upgrade to these updated packages and images when they are available in the appropriate release channel. To check for available updates, use the OpenShift CLI (oc) or web console. Instructions for upgrading a cluster are available at https://docs.redhat.com/en/documentation/openshift_container_platform/4.12/html-single/updating_clusters/index#updating-cluster-within-minor. | Update reference ↗ |
| CVE-2025-40777 | 16 Jul 2025 | 9.20.0 ≤ 9.20.10; 9.21.0 ≤ 9.21.9; 9.20.9-S1 ≤ 9.20.10-S1 | 9.18.0 ≤ 9.18.37; 9.18.11-S1 ≤ 9.18.37-S1 | Update reference ↗ |
| CVE-2025-40776 | 16 Jul 2025 | 9.11.3-S1 ≤ 9.16.50-S1; 9.18.11-S1 ≤ 9.18.37-S1; 9.20.9-S1 ≤ 9.20.10-S1 | 9.0.0 ≤ 9.20.10 | Update reference ↗ |
| CVE-2025-40775 | 21 May 2025 | 9.20.0 ≤ 9.20.8; 9.21.0 ≤ 9.21.7 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-12705 | 29 Jan 2025 | 9.18.0 ≤ 9.18.32; 9.20.0 ≤ 9.20.4; 9.21.0 ≤ 9.21.3; 9.18.11-S1 ≤ 9.18.32-S1 | For OpenShift Container Platform 4.16 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/4.16/release_notes/ocp-4-16-release-notes.html You may download the oc tool and use it to inspect release image metadata for x86_64, s390x, ppc64le, and aarch64 architectures. The image digests may be found at https://quay.io/repository/openshift-release-dev/ocp-release?tab=tags. The sha values for the release are as follows: (For x86_64 architecture) The image digest is sha256:0065822bf39b11e3a3113eb2dee4bddf0a07fe0967892498771bd9728e145ad0 (For s390x architecture) The image digest is sha256:8decf869391dabf7487a3c531675813a15abeadbd542f1d287a9e2a5b5598f2a (For ppc64le architecture) The image digest is sha256:9b45e5b3617ef97ecd5cc03ad142c209f26ce00940c1c9bb6220649c7d697855 (For aarch64 architecture) The image digest is sha256:24c0f2c999616ef69af9a587b1d4b23cad39f376c8e5d784b030ec4644b5938c All OpenShift Container Platform 4.16 users are advised to upgrade to these updated packages and images when they are available in the appropriate release channel. To check for available updates, use the OpenShift CLI (oc) or web console. Instructions for upgrading a cluster are available at https://docs.openshift.com/container-platform/4.16/updating/updating_a_cluster/updating-cluster-cli.html | Update reference ↗ |
| CVE-2024-11187 | 29 Jan 2025 | 9.11.0 ≤ 9.11.37; 9.16.0 ≤ 9.16.50; 9.18.0 ≤ 9.18.32; 9.20.0 ≤ 9.20.4; 9.21.0 ≤ 9.21.3; 9.11.3-S1 ≤ 9.11.37-S1; 9.16.8-S1 ≤ 9.16.50-S1; 9.18.11-S1 ≤ 9.18.32-S1 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2024-4076 | 23 Jul 2024 | 9.16.13 ≤ 9.16.50; 9.18.0 ≤ 9.18.27; 9.19.0 ≤ 9.19.24; 9.11.33-S1 ≤ 9.11.37-S1; 9.16.13-S1 ≤ 9.16.50-S1; 9.18.11-S1 ≤ 9.18.27-S1 | For OpenShift Container Platform 4.13 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/4.13/release_notes/ocp-4-13-release-notes.html You may download the oc tool and use it to inspect release image metadata for x86_64, s390x, ppc64le, and aarch64 architectures. The image digests may be found at https://quay.io/repository/openshift-release-dev/ocp-release?tab=tags. The sha values for the release are (For x86_64 architecture) The image digest is sha256:ab6f574665395d809511db9dc57764358278538eaae248c6d199208b3c30ab7d (For s390x architecture) The image digest is sha256:5d0769628b09763b170b7be275971144dd74034da83b3d8d42ac24dba7b603f3 (For ppc64le architecture) The image digest is sha256:b32a1b7910754ca0babb0ee4c7099e0cd74ed35a05820a64472ebcebdbe57b8c (For aarch64 architecture) The image digest is sha256:4714b66b8fb0ceeca59fb6a696db81559002261bd4a03e7d55c5a3b766e96242 All OpenShift Container Platform 4.13 users are advised to upgrade to these updated packages and images when they are available in the appropriate release channel. To check for available updates, use the OpenShift CLI (oc) or web console. Instructions for upgrading a cluster are available at https://docs.openshift.com/container-platform/4.13/updating/updating-cluster-cli.html | Update reference ↗ |
| CVE-2024-1975 | 23 Jul 2024 | 9.0.0 ≤ 9.11.37; 9.16.0 ≤ 9.16.50; 9.18.0 ≤ 9.18.27; 9.19.0 ≤ 9.19.24; 9.9.3-S1 ≤ 9.11.37-S1; 9.16.8-S1 ≤ 9.16.49-S1; 9.18.11-S1 ≤ 9.18.27-S1 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2024-1737 | 23 Jul 2024 | 9.11.0 ≤ 9.11.37; 9.16.0 ≤ 9.16.50; 9.18.0 ≤ 9.18.27; 9.19.0 ≤ 9.19.24; 9.11.4-S1 ≤ 9.11.37-S1; 9.16.8-S1 ≤ 9.16.50-S1; 9.18.11-S1 ≤ 9.18.27-S1 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2024-0760 | 23 Jul 2024 | 9.18.1 ≤ 9.18.27; 9.19.0 ≤ 9.19.24; 9.18.11-S1 ≤ 9.18.27-S1 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-6516 | 13 Feb 2024 | 9.16.0 ≤ 9.16.45; 9.16.8-S1 ≤ 9.16.45-S1 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-5680 | 13 Feb 2024 | 9.11.3-S1 ≤ 9.11.37-S1; 9.16.8-S1 ≤ 9.16.45-S1; 9.18.11-S1 ≤ 9.18.21-S1 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-5679 | 13 Feb 2024 | 9.16.12 ≤ 9.16.45; 9.18.0 ≤ 9.18.21; 9.19.0 ≤ 9.19.19; 9.16.12-S1 ≤ 9.16.45-S1; 9.18.11-S1 ≤ 9.18.21-S1 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-5517 | 13 Feb 2024 | 9.12.0 ≤ 9.16.45; 9.18.0 ≤ 9.18.21; 9.19.0 ≤ 9.19.19; 9.16.8-S1 ≤ 9.16.45-S1; 9.18.11-S1 ≤ 9.18.21-S1 | No fixed version is explicitly recorded in the structured CVE data. | 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.