Update dependency sigstore to v4 [SECURITY] - #63
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/npm-sigstore-vulnerability
branch
from
July 12, 2026 09:27
59c5378 to
0ecb378
Compare
renovate
Bot
force-pushed
the
renovate/npm-sigstore-vulnerability
branch
2 times, most recently
from
July 30, 2026 18:49
1c3502e to
cb554b6
Compare
renovate
Bot
force-pushed
the
renovate/npm-sigstore-vulnerability
branch
from
August 11, 2026 22:50
cb554b6 to
580caa6
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:
^3.0.0→^4.0.0sigstore's
certificateOIDsverification constraints are silently dropped and never enforcedCVE-2026-48815 / GHSA-52v5-jr5w-gjxr
More information
Details
Summary
The documented
certificateOIDsoption insigstore.verify()is accepted by the public API but discarded before verification, so required certificate extension OIDs are never checked.Details
The public verify options include
certificateOIDsand the documentation says those OID/value pairs “must be present in the certificate’s extension list.” The policy-construction path used bysigstore.verify()andcreateVerifier()only copies the SAN and issuer settings into the verification policy and completely ignorescertificateOIDs.As a result, callers can believe they are constraining verification to certificates carrying specific Fulcio or workload-identifying OIDs, while the actual verifier never receives those constraints. Any bundle that satisfies the remaining checks is accepted even if the required OID extensions are absent or mismatched.
This is reachable from supported usage through the documented
certificateOIDsverify option.PoC
Impact
Applications that rely on
certificateOIDsto restrict which certificates may sign artifacts receive no such protection. Unauthorized certificates that should be rejected on extension policy can be accepted as long as they satisfy the remaining verification checks.Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Release Notes
sigstore/sigstore-js (sigstore)
v4.1.1Compare Source
Patch Changes
7845532: Verification of OID certificate extensionsf074710: Require inclusion promise in Rekor entry when used as timestamp sourceb5aa4f1]7845532]f074710]v4.1.0Compare Source
Minor Changes
eba6a52:verify(bundle[, payload][, options])now returns aSignerobject containing the public key and identity information from the verification.Patch Changes
cee51c0]2042aad]018974e]dea916f]61a4f9e]5ffadc0]5ffadc0]1663b3e]v4.0.0Compare Source
Major Changes
383e200: Drop support for node 18Patch Changes
40395f5]383e200]383e200]383e200]Configuration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.