{"api_version":"v1","generated_at":"2026-10-08T16:10:00+00:00","product":{"cve_count":5,"evidence_gap_note":"Official registry publication history is linked, but a publisher support or retirement boundary has not been established.","id":"security:cve-sigstore-rekor-0f3f4c44e196","lifecycle_state":"evidence_gap","linked_lifecycle_url":"https://lifecycle.blacktree.nl/libraries/npm/rekor","name":"rekor","next_cursor":null,"observations":[{"affected":"rekor: >= 0.3.0, < 1.5.2","affected_versions_present":true,"cve_id":"CVE-2026-48702","cve_url":"https://cve.blacktree.nl/cve/CVE-2026-48702","fixed":"For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/","last_modified":"2026-08-13T15:16:26.293Z","patch_url":"https://access.redhat.com/security/cve/CVE-2026-48702","primary_source":"","published":"2026-08-13T13:14:19.324Z"},{"affected":"< 1.5.0","affected_versions_present":true,"cve_id":"CVE-2026-24117","cve_url":"https://cve.blacktree.nl/cve/CVE-2026-24117","fixed":"1.5.0.","last_modified":"2026-01-23T20:14:54.031Z","patch_url":"https://github.com/sigstore/rekor/commit/60ef2bceba192c5bf9327d003bceea8bf1f8275f","primary_source":"","published":"2026-01-22T22:05:08.136Z"},{"affected":"< 1.5.0","affected_versions_present":true,"cve_id":"CVE-2026-23831","cve_url":"https://cve.blacktree.nl/cve/CVE-2026-23831","fixed":"1.5.0.","last_modified":"2026-01-23T14:32:43.078Z","patch_url":"https://github.com/sigstore/rekor/commit/39bae3d192bce48ef4ef2cbd1788fb5770fee8cd","primary_source":"","published":"2026-01-22T21:26:22.183Z"},{"affected":"< 1.2.0","affected_versions_present":true,"cve_id":"CVE-2023-33199","cve_url":"https://cve.blacktree.nl/cve/CVE-2023-33199","fixed":"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.","last_modified":"2025-01-14T19:07:53.630Z","patch_url":"https://github.com/sigstore/rekor/commit/140c5add105179e5ffd9e3e114fd1b6b93aebbd4","primary_source":"","published":"2023-05-26T22:52:15.973Z"},{"affected":"< 1.1.1","affected_versions_present":true,"cve_id":"CVE-2023-30551","cve_url":"https://cve.blacktree.nl/cve/CVE-2023-30551","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:ca556d3494d08765c90481f15dd965995371168ea7ee7a551000bed4481931c8 (For s390x architecture) The image digest is sha256:77dde49307e9fd00cca6a152f4629039f00ac8c2a729811decb007c4fce73ddb (For ppc64le architecture) The image digest is sha256:10c619d4139ee72c7e3a9007b0d5bcca1517f86a14c7e6e5e74cfcf977f2ada6 (For aarch64 architecture) The image digest is sha256:b2e0ff69918b845d1a1a6c503b764facbfb34afffc64b5dcfb798a385a8f4af5 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","last_modified":"2025-01-29T15:30:31.064Z","patch_url":"https://access.redhat.com/security/cve/CVE-2023-30551","primary_source":"","published":"2023-05-08T15:52:42.446Z"}],"source_generated_at":"2026-10-08T06:18:52.353Z","vendor":"sigstore"}}