← Search results
CVE-LINKED INVENTORY40 SECURITY RECORDS
HashiCorp
Vault
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 vault, 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-5006 | 24 Aug 2026 | 0.11.0 < 2.0.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-12624 | 10 Aug 2026 | < 2.0.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-5051 | 1 Jul 2026 | 1.20.1 < 2.0.1; 1.19.0 < 2.0.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-5807 | 17 Apr 2026 | < 2.0.0; < 2.0.0. | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-4525 | 17 Apr 2026 | 0.11.2 < 2.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-5052 | 17 Apr 2026 | 1.15.0 < 2.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-3605 | 17 Apr 2026 | 0.10.0 < 2.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-12044 | 23 Oct 2025 | 1.20.3 < 1.21.0; 1.19.9 < 1.19.11; 1.18.14 < 1.18.15; 1.16.25 < 1.16.27 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-11621 | 23 Oct 2025 | 0.6.0 < 1.21.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-6203 | 28 Aug 2025 | Vault: 1.15.0 < 1.21.0; Vault Enterprise: 1.15.0 < 1.21.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-6013 | 6 Aug 2025 | 1.10.0 < 1.20.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-6015 | 1 Aug 2025 | 1.10.0 < 1.20.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-6011 | 1 Aug 2025 | < 1.20.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-6004 | 1 Aug 2025 | 1.13.0 < 1.20.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-6037 | 1 Aug 2025 | < 1.20.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-6014 | 1 Aug 2025 | < 1.20.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-6000 | 1 Aug 2025 | 0.8.0 < 1.20.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-5999 | 1 Aug 2025 | 0.10.4 < 1.20.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-4656 | 25 Jun 2025 | 1.14.8 < 1.20.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-3879 | 2 May 2025 | 0.10.0 < 1.19.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-4166 | 2 May 2025 | 0.3.0 < 1.19.2; 0.10.0 < 1.19.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-8185 | 31 Oct 2024 | 1.2.0 < 1.18.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-9180 | 10 Oct 2024 | 0.10.4 < 1.18.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-7594 | 26 Sep 2024 | 1.7.7 < 1.17.6 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-8365 | 2 Sep 2024 | 1.17.3 < 1.17.5; 1.16.7 < 1.17.5 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-6468 | 11 Jul 2024 | 1.10.0 < 1.15.11 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-5798 | 12 Jun 2024 | 0.11.0 < 1.16.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-2660 | 4 Apr 2024 | 1.14.0 < 1.16.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-2048 | 4 Mar 2024 | 1.15.5 < 1.16.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-0831 | 1 Feb 2024 | 1.15.0 ≤ 1.15.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-6337 | 8 Dec 2023 | 1.12.0 < 1.15.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-5954 | 9 Nov 2023 | 1.15.0; 1.15.1; 1.14.3; 1.14.4; 1.14.5; 1.13.7; 1.13.8; 1.13.9 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2023-5077 | 28 Sep 2023 | 0.10.0 < 1.13.0 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2023-4680 | 14 Sep 2023 | 1.14.0 < 1.14.3; 1.13.0 < 1.13.7; 1.12.0 < 1.12.11; 1.6.0 < 1.12.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-3462 | 31 Jul 2023 | 1.13.0 ≤ 1.13.4; 1.14.0 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2023-2121 | 9 Jun 2023 | 1.13.0 < 1.13.3; 1.12.0 < 1.12.7; 1.11.0 < 1.11.11; 1.10.0 < 1.11.0 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2023-0620 | 30 Mar 2023 | 1.13.0 < 1.13.1; 1.12.0 < 1.12.5; 0.8.0 < 1.11.9 | 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:74b23ed4bbb593195a721373ed6693687a9b444c97065ce8ac653ba464375711 (For s390x architecture) The image digest is sha256:a32d509d960eb3e889a22c4673729f95170489789c85308794287e6e9248fb79 (For ppc64le architecture) The image digest is sha256:bca0e4a4ed28b799e860e302c4f6bb7e11598f7c136c56938db0bf9593fb76f8 (For aarch64 architecture) The image digest is sha256:e07e4075c07fca21a1aed9d7f9c165696b1d0fa4940a219a000894e5683d846c 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 Console or the CLI oc command. Instructions for upgrading a cluster are available at https://docs.openshift.com/container-platform/4.13/updating/updating-cluster-cli.html | Update reference ↗ |
| CVE-2023-0665 | 30 Mar 2023 | 1.13.0 < 1.13.1; 1.12.0 < 1.12.5; 1.11.0 < 1.11.9 | 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:74b23ed4bbb593195a721373ed6693687a9b444c97065ce8ac653ba464375711 (For s390x architecture) The image digest is sha256:a32d509d960eb3e889a22c4673729f95170489789c85308794287e6e9248fb79 (For ppc64le architecture) The image digest is sha256:bca0e4a4ed28b799e860e302c4f6bb7e11598f7c136c56938db0bf9593fb76f8 (For aarch64 architecture) The image digest is sha256:e07e4075c07fca21a1aed9d7f9c165696b1d0fa4940a219a000894e5683d846c 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 Console or the CLI oc command. Instructions for upgrading a cluster are available at https://docs.openshift.com/container-platform/4.13/updating/updating-cluster-cli.html | Update reference ↗ |
| CVE-2023-25000 | 30 Mar 2023 | 1.13.0 < 1.13.1; 1.12.0 < 1.12.5; 1.11.0 < 1.11.9; < 1.11.0 | 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:74b23ed4bbb593195a721373ed6693687a9b444c97065ce8ac653ba464375711 (For s390x architecture) The image digest is sha256:a32d509d960eb3e889a22c4673729f95170489789c85308794287e6e9248fb79 (For ppc64le architecture) The image digest is sha256:bca0e4a4ed28b799e860e302c4f6bb7e11598f7c136c56938db0bf9593fb76f8 (For aarch64 architecture) The image digest is sha256:e07e4075c07fca21a1aed9d7f9c165696b1d0fa4940a219a000894e5683d846c 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 Console or the CLI oc command. Instructions for upgrading a cluster are available at https://docs.openshift.com/container-platform/4.13/updating/updating-cluster-cli.html | Update reference ↗ |
| CVE-2023-24999 | 10 Mar 2023 | 1.12.0 < 1.12.4; 1.11.0 < 1.11.8; < 1.10.11 | These updated images include numerous enhancements and bug fixes. Space precludes documenting all of these changes in this advisory. Users are directed to the Red Hat OpenShift Data Foundation Release Notes for information on the most significant of these changes: https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.13/html/4.13_release_notes/index All Red Hat OpenShift Data Foundation users are advised to upgrade to these updated images that provide numerous bug fixes and enhancements. | 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.