Repository navigation
Update module github.com/sigstore/rekor to v1.5.2 [SECURITY] - #365
Open
renovate-update-app[bot] wants to merge 1 commit into
Open
renovate-update-app[bot] wants to merge 1 commit into
renovate-update-app[bot] wants to merge 1 commit into
Conversation
Author
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
![renovatee-approver-stackvista[bot]](https://avatars.githubusercontent.com/u/10511829?s=60&v=4){kind=small}
renovate-update-app
Bot
force-pushed
the
renovate/go-github.com-sigstore-rekor-vulnerability
branch
from
October 24, 2026 08:29
a2da2b3 to
32bf093
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.3.6→v1.5.2Warning
Some dependencies could not be looked up. Check the warning logs for more information.
Rekor's COSE v0.0.1 entry type nil pointer dereference in Canonicalize via empty Message
CVE-2026-23831 / GHSA-273p-m2cw-6833
More information
Details
Summary
Rekor’s cose v0.0.1 entry implementation can panic on attacker-controlled input when canonicalizing a proposed entry with an empty
spec.message.validate()returns nil (success) whenmessageis empty, leavingsign1Msguninitialized, andCanonicalize()later dereferencesv.sign1Msg.Payload.Impact
A malformed proposed entry of the
cose/v0.0.1type 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.Patches
Upgrade to v1.5.0
Workarounds
None
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Rekor affected by Server-Side Request Forgery (SSRF) via provided public key URL
CVE-2026-24117 / GHSA-4c4x-jm2x-pf9j
More information
Details
Summary
/api/v1/index/retrievesupports retrieving a public key via a user-provided URL, allowing attackers to trigger SSRF to arbitrary internal services.Since the SSRF only can trigger GET requests, the request cannot mutate state. The response from the GET request is not returned to the caller so data exfiltration is not possible. A malicious actor could attempt to probe an internal network through Blind SSRF.
Impact
Patches
Upgrade to v1.5.0. Note that this is a breaking change to the search API and fully disables lookups by URL. If you require this feature, please reach out and we can discuss alternatives.
Workarounds
Disable the search endpoint with
--enable_retrieve_api=false.Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Rekor has an OOM Condition due to Unbounded gzip Decompression in Alpine APK Parsing Logic
CVE-2026-48702 / GHSA-47q9-m4ww-924m
More information
Details
Description
The
Package.Unmarshal()function inpkg/types/alpine/apk.godecompresses the signature and control gzip members of an APK file into in-memory buffers without bounding the total decompressed size. The existingmax_apk_metadata_sizecheck (default 1MB) is only applied to individual tar entry header sizes after decompression completes, so it does not prevent a decompression bomb from consuming unbounded heap memory.An attacker can craft a gzip stream that compresses at a ~1000:1 ratio (e.g., 2MB compressed zeros → 2GB decompressed). When submitted as spec.package.content in an Alpine
ProposedEntry, the server decompresses the full payload into memory during request processing, triggering a fatal Go runtime out-of-memory error or OS OOM-kill that cannot be caught by the server's recover() middleware.This is reachable via two unauthenticated endpoints:
Both invoke
V001Entry.Canonicalize()→fetchExternalEntities()→apk.Unmarshal(packageData), which performs the unbounded decompression.Workarounds
There is no effective workaround. Setting
max_request_body_sizereduces but does not eliminate exposure due to the ~1000:1 compression ratio (a 1MB body limit still allows ~1GB heap allocation). Settingmax_apk_metadata_sizehas no effect on this vulnerability since the check is applied after decompression.Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Rekor's COSE v0.0.1 entry type nil pointer dereference in Canonicalize via empty Message
CVE-2026-23831 / GHSA-273p-m2cw-6833 / GO-2026-4354
More information
Details
Summary
Rekor’s cose v0.0.1 entry implementation can panic on attacker-controlled input when canonicalizing a proposed entry with an empty
spec.message.validate()returns nil (success) whenmessageis empty, leavingsign1Msguninitialized, andCanonicalize()later dereferencesv.sign1Msg.Payload.Impact
A malformed proposed entry of the
cose/v0.0.1type 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.Patches
Upgrade to v1.5.0
Workarounds
None
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Rekor affected by Server-Side Request Forgery (SSRF) via provided public key URL
CVE-2026-24117 / GHSA-4c4x-jm2x-pf9j / GO-2026-4355
More information
Details
Summary
/api/v1/index/retrievesupports retrieving a public key via a user-provided URL, allowing attackers to trigger SSRF to arbitrary internal services.Since the SSRF only can trigger GET requests, the request cannot mutate state. The response from the GET request is not returned to the caller so data exfiltration is not possible. A malicious actor could attempt to probe an internal network through Blind SSRF.
Impact
Patches
Upgrade to v1.5.0. Note that this is a breaking change to the search API and fully disables lookups by URL. If you require this feature, please reach out and we can discuss alternatives.
Workarounds
Disable the search endpoint with
--enable_retrieve_api=false.Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Rekor's COSE v0.0.1 entry type nil pointer dereference in Canonicalize via empty Message in github.com/sigstore/rekor
CVE-2026-23831 / GHSA-273p-m2cw-6833 / GO-2026-4354
More information
Details
Rekor's COSE v0.0.1 entry type nil pointer dereference in Canonicalize via empty Message in github.com/sigstore/rekor
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
Rekor affected by Server-Side Request Forgery (SSRF) via provided public key URL in github.com/sigstore/rekor
CVE-2026-24117 / GHSA-4c4x-jm2x-pf9j / GO-2026-4355
More information
Details
Rekor affected by Server-Side Request Forgery (SSRF) via provided public key URL in github.com/sigstore/rekor
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
Rekor has an OOM Condition due to Unbounded gzip Decompression in Alpine APK Parsing Logic
CVE-2026-48702 / GHSA-47q9-m4ww-924m / GO-2026-5778
More information
Details
Description
The
Package.Unmarshal()function inpkg/types/alpine/apk.godecompresses the signature and control gzip members of an APK file into in-memory buffers without bounding the total decompressed size. The existingmax_apk_metadata_sizecheck (default 1MB) is only applied to individual tar entry header sizes after decompression completes, so it does not prevent a decompression bomb from consuming unbounded heap memory.An attacker can craft a gzip stream that compresses at a ~1000:1 ratio (e.g., 2MB compressed zeros → 2GB decompressed). When submitted as spec.package.content in an Alpine
ProposedEntry, the server decompresses the full payload into memory during request processing, triggering a fatal Go runtime out-of-memory error or OS OOM-kill that cannot be caught by the server's recover() middleware.This is reachable via two unauthenticated endpoints:
Both invoke
V001Entry.Canonicalize()→fetchExternalEntities()→apk.Unmarshal(packageData), which performs the unbounded decompression.Workarounds
There is no effective workaround. Setting
max_request_body_sizereduces but does not eliminate exposure due to the ~1000:1 compression ratio (a 1MB body limit still allows ~1GB heap allocation). Settingmax_apk_metadata_sizehas no effect on this vulnerability since the check is applied after decompression.Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Rekor has an OOM Condition due to Unbounded gzip Decompression in Alpine APK Parsing Logic in github.com/sigstore/rekor
CVE-2026-48702 / GHSA-47q9-m4ww-924m / GO-2026-5778
More information
Details
Rekor has an OOM Condition due to Unbounded gzip Decompression in Alpine APK Parsing Logic in github.com/sigstore/rekor
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
Release Notes
sigstore/rekor (github.com/sigstore/rekor)
v1.5.2Compare Source
Features
Bug Fixes
Improvements
v1.5.1Compare Source
Features
Bug Fixes
v1.5.0Compare Source
This release fixes GHSA-273p-m2cw-6833 and GHSA-4c4x-jm2x-pf9j. Note that this
drops support for fetching public keys via URL when querying the search API.
Vulnerability Fixes
Features
v1.4.3Compare Source
This release reduces dependencies for a number of exported packages.
This release also changes the format of the binary and container signature, which is now a
Sigstore bundle. To verify a release, use the
latest Cosign 3.x, verifying with
cosign verify-blob --bundle <artifact>-keyless.sigstore.json <artifact>.Improvements
Documentation
Contributors
v1.4.2Compare Source
This release includes some performance optimizations and a bug fix for publishing events to a pub/sub topic.
Fixes
Contributors
v1.4.1Compare Source
This release includes updated dependencies for known CVEs, as well as some optimizations to minimize gRPC traffic between Rekor and Trillian.
Fixes
Contributors
v1.4.0Compare Source
This is a minor version release given the removal of the stable checkpoint feature. To our knowledge, this was not
used effectively anywhere and therefore was removed from Rekor v1. Witnessing will be added as part of the upcoming
Rekor v2 release.
Features
Fixes
Removed
Contributors
v1.3.10Compare Source
Note that Rekor v1 is in maintenance mode as we are actively developing
its successor, Rekor v2, designed to be easy to maintain and cheaper to operate.. See the
README
for more information.
Features
Fixes / Misc
Contributors
v1.3.9Compare Source
Features
Contributors
v1.3.8Compare Source
Bug Fixes
Quality Enhancements
Contributors
v1.3.7Compare Source
New Features
Bug Fixes
Contributors
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate CLI.