BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-48815High confidence

sigstore-js: `certificateOIDs` verification constraints are silently dropped and never enforced

sigstore · sigstore-js

Official source article: GitHub GHSA-52V5-JR5W-GJXR ↗. Check the applicable product and release in the original source.

7.5HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 13 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Critical, raised one band.upgradedsince 15 Jul 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.19% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs sigstore sigstore-js and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 13 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Open-source package ranges2 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
npmsigstore<= 4.1.04.1.1GitHub advisory ↗upstream repository advisory · 1 Jul 2026
npmsigstoreSEMVER: introduced 0; fixed 4.1.14.1.1OSV record ↗aggregator derived · 10 Sep 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-48815 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitysigstore: Sigstore: Unauthorized certificates accepted due to ignored `certificateOIDs` verification option
13 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • sigstore as a component of Exploit Intelligence
  • sigstore as a component of Red Hat Connectivity Link 1
  • ubi10/nodejs-22 as a component of Red Hat Enterprise Linux 10
  • ubi10/nodejs-22-minimal as a component of Red Hat Enterprise Linux 10
  • ubi10/nodejs-24-minimal as a component of Red Hat Enterprise Linux 10
  • ubi8/nodejs-22 as a component of Red Hat Enterprise Linux 8
  • ubi8/nodejs-22-minimal as a component of Red Hat Enterprise Linux 8
  • ubi8/nodejs-24 as a component of Red Hat Enterprise Linux 8
  • ubi8/nodejs-24-minimal as a component of Red Hat Enterprise Linux 8
  • ubi9/nodejs-22 as a component of Red Hat Enterprise Linux 9
  • ubi9/nodejs-24 as a component of Red Hat Enterprise Linux 9
  • ubi9/nodejs-24-minimal as a component of Red Hat Enterprise Linux 9
Summary
A flaw was found in sigstore. The `certificateOIDs` option, intended to restrict which certificates can sign artifacts, is accepted by the public application programming interface (API) but is not used during the verification process. This allows unauthorized certificates to be accepted, bypassing security policies that rely on specific certificate extension object identifiers (OIDs). As a result, applications that depend on this option for security receive no protection, potentially leading to the acceptance of malicious or untrusted artifacts.
Remediation
Upgrade to sigstore 4.1.1 or later. The majority of products have sigstore-js as a transitive dependency from the npm v10.9.7 package. ``` sh-5.1$ npm ls sigstore npm@10.9.7 /usr/lib/node_modules/npm +-- @npmcli/arborist@8.0.4 | `-- @npmcli/metavuln-calculator@8.0.1 | `-- pacote@20.0.1 | `-- sigstore@3.1.0 deduped +-- libnpmpublish@10.0.2 | `-- sigstore@3.1.0 `-- pacote@19.0.2 `-- sigstore@3.1.0 deduped ```
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-44494

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 13 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

The product does not verify, or incorrectly verifies, the cryptographic signature for data.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The product does not verify, or incorrectly verifies, the cryptographic signature for data.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

CISA Vulnrichment records proof-of-concept exploitation in its SSVC data. BlackTree has not independently executed or validated exploit material.

Likely attack path
a network path → Improper Verification of Cryptographic Signature → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-347 ↗

CWE-347: Improper Verification of Cryptographic Signature. The product does not verify, or incorrectly verifies, the cryptographic signature for data.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.IHighIntegrity impact: A successful attack can cause a major loss.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-347Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
4.1.1.
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
Upgrade to sigstore 4.1.1 or later. The majority of products have sigstore-js as a transitive dependency from the npm v10.9.7 package. ``` sh-5.1$ npm ls sigstore npm@10.9.7 /usr/lib/node_modules/npm +-- @npmcli/arborist@8.0.4 | `-- @npmcli/metavuln-calculator@8.0.1 | `-- pacote@20.0.1 | `-- sigstore@3.1.0 deduped +-- libnpmpublish@10.0.2 | `-- sigstore@3.1.0 `-- pacote@19.0.2 `-- sigstore@3.1.0 deduped ```
04

Evidence and provenance

Published 14 Jul 2026 · Last source change 15 Jul 2026, 12:56 UTC · CWE-347 · Improper Verification of Cryptographic Signature

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-44494
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD not scheduled

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    sigstore as a component of Exploit Intelligence; sigstore as a component of Red Hat Connectivity Link 1; ubi10/nodejs-22 as a component of Red Hat Enterprise Linux 10; ubi10/nodejs-22-minimal as a component of Red Hat Enterprise Linux 10; ubi10/nodejs-24-minimal as a component of Red Hat Enterprise Linux 10; ubi8/nodejs-22 as a component of Red Hat Enterprise Linux 8; ubi8/nodejs-22-minimal as a component of Red Hat Enterprise Linux 8; ubi8/nodejs-24 as a component of Red Hat Enterprise Linux 8; ubi8/nodejs-24-minimal as a component of Red Hat Enterprise Linux 8; ubi9/nodejs-22 as a component of Red Hat Enterprise Linux 9; ubi9/nodejs-24 as a component of Red Hat Enterprise Linux 9; ubi9/nodejs-24-minimal as a component of Red Hat Enterprise Linux 9; sigstore as a component of Red Hat Enterprise Linux AI (RHEL AI) 3; sigstore as a component of Self-service automation portal 2
    After
    sigstore as a component of Exploit Intelligence; sigstore as a component of Red Hat Connectivity Link 1; ubi10/nodejs-22 as a component of Red Hat Enterprise Linux 10; ubi10/nodejs-22-minimal as a component of Red Hat Enterprise Linux 10; ubi10/nodejs-24-minimal as a component of Red Hat Enterprise Linux 10; ubi8/nodejs-22 as a component of Red Hat Enterprise Linux 8; ubi8/nodejs-22-minimal as a component of Red Hat Enterprise Linux 8; ubi8/nodejs-24 as a component of Red Hat Enterprise Linux 8; ubi8/nodejs-24-minimal as a component of Red Hat Enterprise Linux 8; ubi9/nodejs-22 as a component of Red Hat Enterprise Linux 9; ubi9/nodejs-24 as a component of Red Hat Enterprise Linux 9; ubi9/nodejs-24-minimal as a component of Red Hat Enterprise Linux 9; sigstore as a component of Red Hat Enterprise Linux AI (RHEL AI) 3
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-44494↗Vendor CSAF · Red Hat Product Security↗CISA Vulnrichment SSVC evidence↗CVE authority or vendor reference · GitHub GHSA-52V5-JR5W-GJXR↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-48815 · cve.blacktree.nl