Description
Rekor'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.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| sigstore | rekor | < 1.2.0 | — |
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
SUSE
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| SLES 15 SP5 | rekor | 1.2.1-150400.4.12.1 | SUSE-SU-2023:2515-1 |
| SLES 15 SP4 | rekor | 1.2.1-150400.4.12.1 | SUSE-SU-2023:2515-1 |
openSUSE
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| openSUSE Tumbleweed | rekor | 1.2.1-1.1 | openSUSE-SU-2024:12965-1 |
| openSUSE Leap 15.5 | rekor | 1.2.1-150400.4.12.1 | SUSE-SU-2023:2515-1 |
| openSUSE Leap 15.4 | rekor | 1.2.1-150400.4.12.1 | SUSE-SU-2023:2515-1 |
Wolfi
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Wolfi rolling | aactl | 0.4.12-r7 | — |
| Wolfi rolling | skaffold | 2.6.2-r1 | — |
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| Go | github.com/sigstore/rekor | < 1.2.0 | 1.2.0 | GHSA-frqx-jfcm-6jjr |
Advisories 2
- SUSE-SU-2023:2515-1 Security update for rekor SUSE / openSUSE Security Updates · Feb 4, 2026
- openSUSE-SU-2024:12965-1 rekor-1.2.1-1.1 on GA media SUSE / openSUSE Security Updates · Feb 4, 2026