Skip to content

Update dependency sigstore to v4 [SECURITY] - #63

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-sigstore-vulnerability
Open

Update dependency sigstore to v4 [SECURITY]#63
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-sigstore-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
sigstore (source) ^3.0.0^4.0.0 age confidence

sigstore's certificateOIDs verification constraints are silently dropped and never enforced

CVE-2026-48815 / GHSA-52v5-jr5w-gjxr

More information

Details

Summary

The documented certificateOIDs option in sigstore.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 certificateOIDs and the documentation says those OID/value pairs “must be present in the certificate’s extension list.” The policy-construction path used by sigstore.verify() and createVerifier() only copies the SAN and issuer settings into the verification policy and completely ignores certificateOIDs.

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 certificateOIDs verify option.

PoC
const { createVerificationPolicy } = require("sigstore/dist/config");

const policy = createVerificationPolicy({
  certificateIssuer: "https://issuer.example",
  certificateIdentityEmail: "victim@example.com",
  certificateOIDs: {
    "1.2.3.4": "required-value",
  },
});

console.log("certificateOIDs" in policy, JSON.stringify(policy));
// false {"subjectAlternativeName":"victim@example.com","extensions":{"issuer":"https://issuer.example"}}
Impact

Applications that rely on certificateOIDs to 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 Score: 7.5 / 10 (High)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


Release Notes

sigstore/sigstore-js (sigstore)

v4.1.1

Compare Source

Patch Changes

v4.1.0

Compare Source

Minor Changes
  • eba6a52: verify(bundle[, payload][, options]) now returns a Signer object containing the public key and identity information from the verification.
Patch Changes

v4.0.0

Compare Source

Major Changes
  • 383e200: Drop support for node 18
Patch Changes

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • 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 was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/npm-sigstore-vulnerability branch from 59c5378 to 0ecb378 Compare July 12, 2026 09:27
@renovate
renovate Bot force-pushed the renovate/npm-sigstore-vulnerability branch 2 times, most recently from 1c3502e to cb554b6 Compare July 30, 2026 18:49
@renovate
renovate Bot force-pushed the renovate/npm-sigstore-vulnerability branch from cb554b6 to 580caa6 Compare August 11, 2026 22:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants