Rekor's goals are to provide an immutable tamper resistant ledger of metadata generated within a software…
Historical advisory recorded 24 Oct 2026 22:17:15 UTC. Read the latest advisory.
nvd · CVE-2023-33199
PublishedRekor's goals are to provide an immutable tamper resistant ledger of metadata generated within a software projects supply chain. A malformed proposed entry of the `intoto/v0.0.2` type can cause a panic on a thread within the Rekor process. The thread is recovered so the client receives a 500 error message and service still continues, so the availability impact of this is minimal. This has been fixed in v1.2.0 of Rekor. Users are advised to upgrade. There are no known workarounds for this vulnerability.
Read the publisher's advisoryAffected versions, risk and source history
nvd · CVE-2023-33199
PublishedNVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Modified
Weakness classifications: CWE-617
Original publisher date fields
published: 2023-05-26T23:15:18.960
lastModified: 2026-06-17T06:01:17.550
1 source CPE criteria · context only
- cpe:2.3:a:linuxfoundation:rekor:*:*:*:*:*:*:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
Original source record · Cite this exact observation · Complete original publisher JSON