Skip to content

fix(deps): update module github.com/sigstore/rekor to v1.5.2 [security] (alauda-v2.6.2) - #51

Open
alaudaa-renovate[bot] wants to merge 1 commit into
alauda-v2.6.2from
renovate/alauda-v2.6.2-go-github.com-sigstore-rekor-vulnerability
Open

fix(deps): update module github.com/sigstore/rekor to v1.5.2 [security] (alauda-v2.6.2)#51
alaudaa-renovate[bot] wants to merge 1 commit into
alauda-v2.6.2from
renovate/alauda-v2.6.2-go-github.com-sigstore-rekor-vulnerability

Conversation

@alaudaa-renovate

@alaudaa-renovate alaudaa-renovate Bot commented Jul 3, 2026

Copy link
Copy Markdown

This PR contains the following updates:

Package Change Age Confidence
github.com/sigstore/rekor v1.5.0 -> v1.5.2 age confidence

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 in pkg/types/alpine/apk.go decompresses the signature and control gzip members of an APK file into in-memory buffers without bounding the total decompressed size. The existing max_apk_metadata_size check (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:

  • POST /api/v1/log/entries (createLogEntry)
  • POST /api/v1/log/entries/retrieve (searchLogQuery)

Both invoke V001Entry.Canonicalize()fetchExternalEntities()apk.Unmarshal(packageData), which performs the unbounded decompression.

Workarounds

There is no effective workaround. Setting max_request_body_size reduces but does not eliminate exposure due to the ~1000:1 compression ratio (a 1MB body limit still allows ~1GB heap allocation). Setting max_apk_metadata_size has no effect on this vulnerability since the check is applied after decompression.

Severity

  • CVSS Score: 7.5 / 10 (High)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

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.2

Compare Source

Features

  • Support restricting kinds on insertion (#​2814)

Bug Fixes

  • alpine: Enforce max size limit on decompression (#​2831)
  • fix(trillianclient): strip dns:/// scheme from TLS ServerName in gRPC dial (#​2812)
  • Fix internal error detail leakage in 500 responses (#​2801)
  • add checks to ensure returned entries match client inputs to rekor-cli (#​2799)
  • add defensive check to ensure tid is in config ahead of getting client (#​2795)
  • add nil pointer check to resolve fuzzing crash (#​2807)

Improvements

  • restapi: include inactiveShards in the homepage total count (#​2797)
  • client: surface last-response details after retries are exhausted (#​2796)

v1.5.1

Compare Source

Features

  • optimize memory for DSSE v0.0.1 processing (#​2766)

Bug Fixes

  • Type assert the entry bundle when verifying inclusion proof (#​2755)
  • return correct errors in rare failure situations (#​2753)
  • raise error if decoding hash fails during inclusion proof (#​2754)

Configuration

📅 Schedule: Branch creation - "" in timezone Asia/Shanghai, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@alaudaa-renovate

Copy link
Copy Markdown
Author

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 57 additional dependencies were updated

Details:

Package Change
github.com/go-openapi/runtime v0.29.3 -> v0.29.4
github.com/go-openapi/strfmt v0.26.1 -> v0.26.2
github.com/go-openapi/swag v0.25.5 -> v0.26.0
github.com/go-openapi/swag/conv v0.25.5 -> v0.26.0
github.com/secure-systems-lab/go-securesystemslib v0.10.0 -> v0.11.0
github.com/sigstore/protobuf-specs v0.5.0 -> v0.5.1
github.com/sigstore/sigstore v1.10.5 -> v1.10.6
github.com/sigstore/sigstore/pkg/signature/kms/aws v1.10.5 -> v1.10.6
github.com/sigstore/sigstore/pkg/signature/kms/azure v1.10.5 -> v1.10.6
github.com/sigstore/sigstore/pkg/signature/kms/gcp v1.10.5 -> v1.10.6
github.com/sigstore/sigstore/pkg/signature/kms/hashivault v1.10.5 -> v1.10.6
google.golang.org/api v0.272.0 -> v0.274.0
k8s.io/api v0.34.1 -> v0.35.3
k8s.io/apimachinery v0.34.1 -> v0.35.3
k8s.io/client-go v0.34.1 -> v0.35.3
k8s.io/utils v0.0.0-20250820121507-0af2bda4dd1d -> v0.0.0-20251002143259-bc988d571ff4
cloud.google.com/go/auth v0.18.2 -> v0.19.0
cloud.google.com/go/iam v1.5.3 -> v1.7.0
cloud.google.com/go/kms v1.26.0 -> v1.28.0
cloud.google.com/go/longrunning v0.8.0 -> v0.9.0
github.com/aws/aws-sdk-go-v2 v1.41.4 -> v1.41.6
github.com/aws/aws-sdk-go-v2/config v1.32.12 -> v1.32.14
github.com/aws/aws-sdk-go-v2/credentials v1.19.12 -> v1.19.14
github.com/aws/aws-sdk-go-v2/feature/ec2/imds v1.18.20 -> v1.18.21
github.com/aws/aws-sdk-go-v2/internal/configsources v1.4.20 -> v1.4.22
github.com/aws/aws-sdk-go-v2/internal/endpoints/v2 v2.7.20 -> v2.7.22
github.com/aws/aws-sdk-go-v2/service/internal/presigned-url v1.13.20 -> v1.13.21
github.com/aws/aws-sdk-go-v2/service/kms v1.50.3 -> v1.50.5
github.com/aws/aws-sdk-go-v2/service/signin v1.0.8 -> v1.0.9
github.com/aws/aws-sdk-go-v2/service/sso v1.30.13 -> v1.30.15
github.com/aws/aws-sdk-go-v2/service/ssooidc v1.35.17 -> v1.35.19
github.com/aws/aws-sdk-go-v2/service/sts v1.41.9 -> v1.41.10
github.com/aws/smithy-go v1.24.2 -> v1.25.0
github.com/go-openapi/analysis v0.24.3 -> v0.25.0
github.com/go-openapi/swag/cmdutils v0.25.5 -> v0.26.0
github.com/go-openapi/swag/fileutils v0.25.5 -> v0.26.0
github.com/go-openapi/swag/jsonname v0.25.5 -> v0.26.0
github.com/go-openapi/swag/jsonutils v0.25.5 -> v0.26.0
github.com/go-openapi/swag/loading v0.25.5 -> v0.26.0
github.com/go-openapi/swag/mangling v0.25.5 -> v0.26.0
github.com/go-openapi/swag/netutils v0.25.5 -> v0.26.0
github.com/go-openapi/swag/stringutils v0.25.5 -> v0.26.0
github.com/go-openapi/swag/typeutils v0.25.5 -> v0.26.0
github.com/go-openapi/swag/yamlutils v0.25.5 -> v0.26.0
github.com/google/trillian v1.7.2 -> v1.7.3
github.com/googleapis/gax-go/v2 v2.19.0 -> v2.22.0
go.step.sm/crypto v0.77.2 -> v0.77.7
go.uber.org/zap v1.27.1 -> v1.28.0
google.golang.org/genproto v0.0.0-20260316180232-0b37fe3546d5 -> v0.0.0-20260319201613-d00831a3d3e7
google.golang.org/genproto/googleapis/api v0.0.0-20260316180232-0b37fe3546d5 -> v0.0.0-20260401024825-9d38bb4040a9
google.golang.org/genproto/googleapis/rpc v0.0.0-20260316180232-0b37fe3546d5 -> v0.0.0-20260401024825-9d38bb4040a9
google.golang.org/grpc v1.79.3 -> v1.80.0
gopkg.in/evanphx/json-patch.v4 v4.12.0 -> v4.13.0
gopkg.in/ini.v1 v1.67.1 -> v1.67.2
k8s.io/klog/v2 v2.130.1 -> v2.140.0
k8s.io/kube-openapi v0.0.0-20250710124328-f3f2b991d03b -> v0.0.0-20250910181357-589584f1c912
sigs.k8s.io/json v0.0.0-20241014173422-cfa47c3a1cc8 -> v0.0.0-20250730193827-2d320260d730

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant