GHSA-52v5-jr5w-gjxr

### 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

```javascript 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.