CVE-2026-48815
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedsigstore-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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe sigstore-js library's sigstore.verify() function accepts a certificateOIDs parameter intended to restrict which certificate extension OIDs are permitted for artifact signing verification, but this parameter is silently discarded before verification occurs. This allows any certificate to be accepted even when the application explicitly configured OID restrictions, bypassing a security control.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify sigstore-js versionRun 'npm list sigstore-js' or check package.json dependencies to find the installed version of sigstore-jsAffected if The installed version is lower than 4.1.1
-
Locate verify() calls with certificateOIDsSearch codebase for instances of sigstore.verify() that include a certificateOIDs parameter in the options objectAffected if The code uses verify() with certificateOIDs configured for OID restriction
-
Verify OID restriction behaviorTest that only certificates with the specified OID extensions are accepted by the verify() function - attempt verification with a certificate missing the configured OIDsAffected if Verification succeeds with certificates that should be rejected based on the configured certificateOIDs restriction (parameter is being ignored)
-
Confirm dependency treeCheck if sigstore-js is a transitive dependency by running 'npm why sigstore-js' to see which packages depend on itAffected if sigstore-js lower than 4.1.1 is present anywhere in the dependency tree
The environment is affected if sigstore-js version is below 4.1.1 AND the application uses sigstore.verify() with certificateOIDs configured, since the OID restriction will be silently ignored.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade sigstore-js to version 4.1.1 or later to ensure the certificateOIDs option is properly enforced during verification.
sigstore-js version 4.1.1 or later
- Upgrade sigstore-js to version 4.1.1 or later using your package manager (npm install sigstore@^4.1.1, yarn add sigstore@^4.1.1, or pnpm add sigstore@^4.1.1)
- After upgrading, verify the certificateOIDs option is now properly enforced during sigstore.verify() calls
- Test that artifact verification still functions correctly with the updated library
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-48815 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-48815 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data