{"api_version":"v1","generated_at":"2026-10-08T04:50:00+00:00","product":{"cve_count":40,"evidence_gap_note":"Official registry publication history is linked, but a publisher support or retirement boundary has not been established.","id":"security:cve-hashicorp-vault-c61898d63a80","lifecycle_state":"evidence_gap","linked_lifecycle_url":"https://lifecycle.blacktree.nl/libraries/npm/vault","name":"Vault","next_cursor":null,"observations":[{"affected":"0.11.0 < 2.0.4","affected_versions_present":true,"cve_id":"CVE-2026-5006","cve_url":"https://cve.blacktree.nl/cve/CVE-2026-5006","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2026-08-26T03:56:14.745Z","patch_url":"","primary_source":"","published":"2026-08-24T20:32:49.396Z"},{"affected":"< 2.0.3","affected_versions_present":true,"cve_id":"CVE-2026-12624","cve_url":"https://cve.blacktree.nl/cve/CVE-2026-12624","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2026-08-11T15:52:34.653Z","patch_url":"","primary_source":"","published":"2026-08-10T17:00:46.283Z"},{"affected":"1.20.1 < 2.0.1; 1.19.0 < 2.0.1","affected_versions_present":true,"cve_id":"CVE-2026-5051","cve_url":"https://cve.blacktree.nl/cve/CVE-2026-5051","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2026-07-01T17:54:43.314Z","patch_url":"","primary_source":"","published":"2026-07-01T17:10:56.918Z"},{"affected":"< 2.0.0; < 2.0.0.","affected_versions_present":true,"cve_id":"CVE-2026-5807","cve_url":"https://cve.blacktree.nl/cve/CVE-2026-5807","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2026-07-15T00:41:55.881Z","patch_url":"","primary_source":"","published":"2026-04-17T03:22:13.816Z"},{"affected":"0.11.2 < 2.0.0","affected_versions_present":true,"cve_id":"CVE-2026-4525","cve_url":"https://cve.blacktree.nl/cve/CVE-2026-4525","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2026-07-15T00:52:47.241Z","patch_url":"","primary_source":"","published":"2026-04-17T03:00:47.561Z"},{"affected":"1.15.0 < 2.0.0","affected_versions_present":true,"cve_id":"CVE-2026-5052","cve_url":"https://cve.blacktree.nl/cve/CVE-2026-5052","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2026-04-17T17:57:55.377Z","patch_url":"","primary_source":"","published":"2026-04-17T02:55:25.080Z"},{"affected":"0.10.0 < 2.0.0","affected_versions_present":true,"cve_id":"CVE-2026-3605","cve_url":"https://cve.blacktree.nl/cve/CVE-2026-3605","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2026-07-15T01:02:36.165Z","patch_url":"","primary_source":"","published":"2026-04-17T02:44:42.032Z"},{"affected":"1.20.3 < 1.21.0; 1.19.9 < 1.19.11; 1.18.14 < 1.18.15; 1.16.25 < 1.16.27","affected_versions_present":true,"cve_id":"CVE-2025-12044","cve_url":"https://cve.blacktree.nl/cve/CVE-2025-12044","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-10-23T20:00:16.601Z","patch_url":"","primary_source":"","published":"2025-10-23T19:15:16.567Z"},{"affected":"0.6.0 < 1.21.0","affected_versions_present":true,"cve_id":"CVE-2025-11621","cve_url":"https://cve.blacktree.nl/cve/CVE-2025-11621","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2026-02-26T16:57:11.235Z","patch_url":"","primary_source":"","published":"2025-10-23T19:08:54.989Z"},{"affected":"Vault: 1.15.0 < 1.21.0; Vault Enterprise: 1.15.0 < 1.21.2","affected_versions_present":true,"cve_id":"CVE-2025-6203","cve_url":"https://cve.blacktree.nl/cve/CVE-2025-6203","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-10-23T18:18:34.361Z","patch_url":"","primary_source":"","published":"2025-08-28T19:36:09.870Z"},{"affected":"1.10.0 < 1.20.2","affected_versions_present":true,"cve_id":"CVE-2025-6013","cve_url":"https://cve.blacktree.nl/cve/CVE-2025-6013","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2026-02-26T17:49:53.769Z","patch_url":"","primary_source":"","published":"2025-08-06T10:06:55.668Z"},{"affected":"1.10.0 < 1.20.1","affected_versions_present":true,"cve_id":"CVE-2025-6015","cve_url":"https://cve.blacktree.nl/cve/CVE-2025-6015","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-08-01T18:35:17.893Z","patch_url":"","primary_source":"","published":"2025-08-01T18:03:53.214Z"},{"affected":"< 1.20.1","affected_versions_present":true,"cve_id":"CVE-2025-6011","cve_url":"https://cve.blacktree.nl/cve/CVE-2025-6011","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-08-01T19:06:58.251Z","patch_url":"","primary_source":"","published":"2025-08-01T18:00:24.528Z"},{"affected":"1.13.0 < 1.20.1","affected_versions_present":true,"cve_id":"CVE-2025-6004","cve_url":"https://cve.blacktree.nl/cve/CVE-2025-6004","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-08-01T19:11:52.729Z","patch_url":"","primary_source":"","published":"2025-08-01T17:56:00.780Z"},{"affected":"< 1.20.1","affected_versions_present":true,"cve_id":"CVE-2025-6037","cve_url":"https://cve.blacktree.nl/cve/CVE-2025-6037","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2026-02-26T17:50:09.821Z","patch_url":"","primary_source":"","published":"2025-08-01T17:52:48.778Z"},{"affected":"< 1.20.1","affected_versions_present":true,"cve_id":"CVE-2025-6014","cve_url":"https://cve.blacktree.nl/cve/CVE-2025-6014","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-08-01T18:05:37.553Z","patch_url":"","primary_source":"","published":"2025-08-01T17:50:09.308Z"},{"affected":"0.8.0 < 1.20.1","affected_versions_present":true,"cve_id":"CVE-2025-6000","cve_url":"https://cve.blacktree.nl/cve/CVE-2025-6000","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-08-01T18:12:02.883Z","patch_url":"","primary_source":"","published":"2025-08-01T17:40:48.524Z"},{"affected":"0.10.4 < 1.20.0","affected_versions_present":true,"cve_id":"CVE-2025-5999","cve_url":"https://cve.blacktree.nl/cve/CVE-2025-5999","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-08-01T18:08:59.605Z","patch_url":"","primary_source":"","published":"2025-08-01T17:38:58.409Z"},{"affected":"1.14.8 < 1.20.0","affected_versions_present":true,"cve_id":"CVE-2025-4656","cve_url":"https://cve.blacktree.nl/cve/CVE-2025-4656","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-06-25T20:05:45.581Z","patch_url":"","primary_source":"","published":"2025-06-25T16:15:11.861Z"},{"affected":"0.10.0 < 1.19.1","affected_versions_present":true,"cve_id":"CVE-2025-3879","cve_url":"https://cve.blacktree.nl/cve/CVE-2025-3879","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-05-02T16:50:15.195Z","patch_url":"","primary_source":"","published":"2025-05-02T16:15:10.650Z"},{"affected":"0.3.0 < 1.19.2; 0.10.0 < 1.19.2","affected_versions_present":true,"cve_id":"CVE-2025-4166","cve_url":"https://cve.blacktree.nl/cve/CVE-2025-4166","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-05-08T13:01:48.440Z","patch_url":"","primary_source":"","published":"2025-05-02T14:57:58.710Z"},{"affected":"1.2.0 < 1.18.1","affected_versions_present":true,"cve_id":"CVE-2024-8185","cve_url":"https://cve.blacktree.nl/cve/CVE-2024-8185","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2024-10-31T17:11:35.647Z","patch_url":"","primary_source":"","published":"2024-10-31T15:14:55.145Z"},{"affected":"0.10.4 < 1.18.0","affected_versions_present":true,"cve_id":"CVE-2024-9180","cve_url":"https://cve.blacktree.nl/cve/CVE-2024-9180","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2024-11-08T22:27:31.042Z","patch_url":"","primary_source":"","published":"2024-10-10T20:54:57.084Z"},{"affected":"1.7.7 < 1.17.6","affected_versions_present":true,"cve_id":"CVE-2024-7594","cve_url":"https://cve.blacktree.nl/cve/CVE-2024-7594","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-01-10T13:06:49.543Z","patch_url":"","primary_source":"","published":"2024-09-26T19:52:55.652Z"},{"affected":"1.17.3 < 1.17.5; 1.16.7 < 1.17.5","affected_versions_present":true,"cve_id":"CVE-2024-8365","cve_url":"https://cve.blacktree.nl/cve/CVE-2024-8365","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2024-09-04T17:18:36.980Z","patch_url":"","primary_source":"","published":"2024-09-02T01:30:56.618Z"},{"affected":"1.10.0 < 1.15.11","affected_versions_present":true,"cve_id":"CVE-2024-6468","cve_url":"https://cve.blacktree.nl/cve/CVE-2024-6468","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2024-08-01T21:41:03.514Z","patch_url":"","primary_source":"","published":"2024-07-11T20:40:12.298Z"},{"affected":"0.11.0 < 1.16.2","affected_versions_present":true,"cve_id":"CVE-2024-5798","cve_url":"https://cve.blacktree.nl/cve/CVE-2024-5798","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-11-04T16:30:51.697Z","patch_url":"","primary_source":"","published":"2024-06-12T18:55:24.788Z"},{"affected":"1.14.0 < 1.16.0","affected_versions_present":true,"cve_id":"CVE-2024-2660","cve_url":"https://cve.blacktree.nl/cve/CVE-2024-2660","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2024-09-26T00:13:17.242Z","patch_url":"","primary_source":"","published":"2024-04-04T17:55:20.192Z"},{"affected":"1.15.5 < 1.16.0","affected_versions_present":true,"cve_id":"CVE-2024-2048","cve_url":"https://cve.blacktree.nl/cve/CVE-2024-2048","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-02-13T17:32:32.417Z","patch_url":"","primary_source":"","published":"2024-03-04T19:56:47.253Z"},{"affected":"1.15.0 \u2264 1.15.4","affected_versions_present":true,"cve_id":"CVE-2024-0831","cve_url":"https://cve.blacktree.nl/cve/CVE-2024-0831","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-02-13T17:27:29.010Z","patch_url":"","primary_source":"","published":"2024-02-01T01:41:33.801Z"},{"affected":"1.12.0 < 1.15.4","affected_versions_present":true,"cve_id":"CVE-2023-6337","cve_url":"https://cve.blacktree.nl/cve/CVE-2023-6337","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-02-13T17:26:18.153Z","patch_url":"","primary_source":"","published":"2023-12-08T21:12:31.712Z"},{"affected":"1.15.0; 1.15.1; 1.14.3; 1.14.4; 1.14.5; 1.13.7; 1.13.8; 1.13.9","affected_versions_present":true,"cve_id":"CVE-2023-5954","cve_url":"https://cve.blacktree.nl/cve/CVE-2023-5954","fixed":"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","last_modified":"2025-02-13T17:25:58.499Z","patch_url":"https://access.redhat.com/security/cve/CVE-2023-5954","primary_source":"","published":"2023-11-09T20:13:49.346Z"},{"affected":"0.10.0 < 1.13.0","affected_versions_present":true,"cve_id":"CVE-2023-5077","cve_url":"https://cve.blacktree.nl/cve/CVE-2023-5077","fixed":"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","last_modified":"2024-09-26T21:57:22.469Z","patch_url":"https://access.redhat.com/security/cve/CVE-2023-5077","primary_source":"","published":"2023-09-28T23:24:28.643Z"},{"affected":"1.14.0 < 1.14.3; 1.13.0 < 1.13.7; 1.12.0 < 1.12.11; 1.6.0 < 1.12.0","affected_versions_present":true,"cve_id":"CVE-2023-4680","cve_url":"https://cve.blacktree.nl/cve/CVE-2023-4680","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2024-09-26T17:38:48.629Z","patch_url":"","primary_source":"","published":"2023-09-14T23:06:24.546Z"},{"affected":"1.13.0 \u2264 1.13.4; 1.14.0","affected_versions_present":true,"cve_id":"CVE-2023-3462","cve_url":"https://cve.blacktree.nl/cve/CVE-2023-3462","fixed":"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","last_modified":"2024-10-21T18:04:40.093Z","patch_url":"https://access.redhat.com/security/cve/CVE-2023-3462","primary_source":"","published":"2023-07-31T22:40:23.432Z"},{"affected":"1.13.0 < 1.13.3; 1.12.0 < 1.12.7; 1.11.0 < 1.11.11; 1.10.0 < 1.11.0","affected_versions_present":true,"cve_id":"CVE-2023-2121","cve_url":"https://cve.blacktree.nl/cve/CVE-2023-2121","fixed":"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","last_modified":"2025-01-06T18:15:00.958Z","patch_url":"https://access.redhat.com/security/cve/CVE-2023-2121","primary_source":"","published":"2023-06-09T16:59:49.065Z"},{"affected":"1.13.0 < 1.13.1; 1.12.0 < 1.12.5; 0.8.0 < 1.11.9","affected_versions_present":true,"cve_id":"CVE-2023-0620","cve_url":"https://cve.blacktree.nl/cve/CVE-2023-0620","fixed":"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","last_modified":"2025-02-13T16:39:02.965Z","patch_url":"https://access.redhat.com/security/cve/CVE-2023-0620","primary_source":"","published":"2023-03-30T00:28:13.301Z"},{"affected":"1.13.0 < 1.13.1; 1.12.0 < 1.12.5; 1.11.0 < 1.11.9","affected_versions_present":true,"cve_id":"CVE-2023-0665","cve_url":"https://cve.blacktree.nl/cve/CVE-2023-0665","fixed":"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","last_modified":"2025-02-13T16:39:04.425Z","patch_url":"https://access.redhat.com/security/cve/CVE-2023-0665","primary_source":"","published":"2023-03-30T00:21:47.676Z"},{"affected":"1.13.0 < 1.13.1; 1.12.0 < 1.12.5; 1.11.0 < 1.11.9; < 1.11.0","affected_versions_present":true,"cve_id":"CVE-2023-25000","cve_url":"https://cve.blacktree.nl/cve/CVE-2023-25000","fixed":"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","last_modified":"2025-02-13T16:44:28.625Z","patch_url":"https://access.redhat.com/security/cve/CVE-2023-25000","primary_source":"","published":"2023-03-30T00:17:46.230Z"},{"affected":"1.12.0 < 1.12.4; 1.11.0 < 1.11.8; < 1.10.11","affected_versions_present":true,"cve_id":"CVE-2023-24999","cve_url":"https://cve.blacktree.nl/cve/CVE-2023-24999","fixed":"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.","last_modified":"2025-03-03T20:46:23.638Z","patch_url":"https://access.redhat.com/security/cve/CVE-2023-24999","primary_source":"","published":"2023-03-10T23:12:47.638Z"}],"source_generated_at":"2026-10-07T06:21:30.017Z","vendor":"HashiCorp"}}