Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…
EPSS 0.2%top 90%

Core: CWE-347: Improper Verification of Cryptographic Signature in sigstore sigstore-js (CVE-2026-48758)

0
Medium
Published: 07/14/2026 (07/14/2026, 20:36:28 UTC)
Source: GCVE Database
Vendor/Project: sigstore
Product: sigstore-js

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.

CVSS v3.1

Score 5.4medium

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

Affected software

npmghsa
@sigstore/core
Affected versions
<3.2.1

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 07/15/2026, 07:56:26 UTC

Technical Analysis

A vulnerability exists in the @sigstore/core package's preAuthEncoding function where the use of Node.js 'ascii' encoding truncates characters above U+00FF, allowing Unicode characters to produce the same encoded bytes as ASCII characters. This flaw permits mutation of the DSSE payloadType after signing without invalidating the signature, violating the DSSE type-binding guarantee. The issue affects all versions before 3.2.1.

Potential Impact

An attacker with limited privileges (PR:L) can modify the DSSE payloadType after signing without invalidating the signature, potentially leading to integrity issues. The vulnerability does not impact confidentiality but can affect the integrity and availability of the signed data. No known exploits are reported in the wild.

Mitigation Recommendations

A fix is available in version 3.2.1 of @sigstore/core. Users should upgrade to version 3.2.1 or later to remediate this vulnerability. No other mitigations are indicated.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
GHSA-jfc7-64v2-mr8c
Osv Schema Version
1.4.0
Aliases
["CVE-2026-48758"]
Ecosystems
["npm"]
Database Specific Severity
MODERATE
Cvss Version
3.1

Threat ID: 6a3ef78d27e9c79719ff493d

Added to database: 06/26/2026, 22:05:01 UTC

Last enriched: 07/15/2026, 07:56:26 UTC

Last updated: 07/31/2026, 19:22:59 UTC

Views: 129

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses