Most recent entries from all

CLEANSTART-2026-AZ47953 — Security fix for CVE-2026-48815 applied in: pulumi 3.248.0-r0, renovate 44.31.0-r2, renovate 44.32.4-r1, renovate 44.32…

Affected: CleanStart: pulumi, CleanStart: renovate

CVE-2026-48815 affects multiple packages. This issue is resolved in later releases. See references for individual vulnerability details.

EUVD-2026-337882

fkie_cve-2026-48815

sigstore-js provides JavaScript libraries for interacting with Sigstore services. Prior to 4.1.1, 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 and applications relying on certificateOIDs to restrict which certificates may sign artifacts can accept unauthorized certificates. This issue is fixed in version 4.1.1.

GHSA-52v5-jr5w-gjxr — sigstore's `certificateOIDs` verification constraints are silently dropped and never enforced

Affected: npm: sigstore

### 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 `certific…