CVE-2026-48758

sigstore-js: DSSE payloadType type-binding failure

Published Jul 14, 2026 CVSS 3.1 · 5.4 Medium EPSS < 1% KEV · Not listed
Description
sigstore-js provides JavaScript libraries for interacting with Sigstore services. Prior to 3.2.1, the preAuthEncoding function in @sigstore/core uses Node.js ascii encoding when converting the PAE string to bytes, allowing payloadType to be mutated after signing without invalidating the signature and breaking the type-binding guarantee that DSSE is designed to provide. This issue is fixed in version 3.2.1.

Analysis

AI-generated

Technical impact

The vulnerability lies in the preAuthEncoding function of @sigstore/core prior to version 3.2.1, where Node.js ascii encoding converts the Pre‑Authentication Encoding string to bytes in a way that allows the payloadType field to be altered after the signature has been created. This type‑binding failure (CWE‑347) breaks DSSE’s guarantee that the payload type remains unchanged, enabling an attacker to present a modified artifact as authentic without invalidating the signature.

Affected Systems

The affected product is sigstore-js, a JavaScript library suite for interacting with Sigstore services. All releases that incorporate @sigstore/core before version 3.2.1 are vulnerable.

Risk and Exploitability

The CVSS score of 5.4 indicates moderate severity, and the EPSS score of under 1 % implies a low likelihood of exploitation currently. The vulnerability is not listed in the CISA KEV catalog. Exploitation requires the vulnerable library to be used in an environment where a payloadType can be altered after signature generation, so the risk is limited to dependency‑based scenarios rather than a broad network attack surface.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade sigstore-js to a release that includes @sigstore/core 3.2.1 or later
  • Audit project dependencies to confirm all instances of @sigstore/core are at 3.2.1 or newer
  • In application code, validate that the payloadType remains unchanged before signature verification to enforce DSSE type‑binding

Generated by OpenCVE AI on August 1, 2026 at 09:12 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-jfc7-64v2-mr8c @sigstore/core has DSSE payloadType type-binding failure
History
Type Values Removed Values Added
First Time appeared Sigstore
Sigstore sigstore
Vendors & Products Sigstore
Sigstore sigstore
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description sigstore-js provides JavaScript libraries for interacting with Sigstore services. Prior to 3.2.1, the preAuthEncoding function in @sigstore/core uses Node.js ascii encoding when converting the PAE string to bytes, allowing payloadType to be mutated after signing without invalidating the signature and breaking the type-binding guarantee that DSSE is designed to provide. This issue is fixed in version 3.2.1.
Title sigstore-js: DSSE payloadType type-binding failure
Weaknesses CWE-347
References
Metrics cvssV3_1

{'score': 5.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L'}

Weaknesses
  • CWE-347

    Improper Verification of Cryptographic Signature

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jul 15, 2026, 12:54 PM
Reserved
May 22, 2026, 7:39 PM
Status
Deferred
Published
Jul 14, 2026, 9:17 PM
Modified
Oct 24, 2026, 9:10 PM
Severity
Moderate
Public date
Jun 26, 2026, 7:11 PM