Sigstore Js
Approved changes feed: RSS · Atom
cpe:2.3:a:sigstore:sigstore-js:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Sigstore (534c4401-0625-5be2-ae9b-f6c1539e71bc) |
|---|---|
| Product | Sigstore Js (60548f0d-cc5d-57f9-8459-a7ef1cb4c9d8) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-59891 |
vulnerable | 2026-07-29 01:03:18.045062 |
Credential confusion in @sigstore/oci can leak registry credentials to an attacker-controlled registry
CRITICAL (9.6)
sigstore-js provides JavaScript libraries for interacting with Sigstore services. Prior to 0.7.1, getRegistryCredentials() reads credentials from the Docker config file and selects an entry by checking whether any configured auth key contains the target registry string. Because this is a substring match rather than an exact host match, credentials configured for one registry can be selected for and transmitted to a different registry whose hostname has a substring relationship with a configured auth key. This issue is fixed in version 0.7.1.
Published: 2026-07-14T16:54:50.608Z
Updated: 2026-07-21T18:43:52.659Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-48816 |
vulnerable | 2026-07-29 00:55:01.665904 |
sigstore-js: Insufficient Verification of Data Authenticity
MEDIUM (6.5)
sigstore-js provides JavaScript libraries for interacting with Sigstore services. Prior to 3.1.1, @sigstore/verify derives a transparency-log timestamp from tlogEntries[].integratedTime for bundle v0.2 inclusionProof-only entries even though the inclusion proof path does not cryptographically bind integratedTime, allowing an attacker who can supply an untrusted bundle to influence certificate validity and timestampThreshold verification decisions. This issue is fixed in version 3.1.1.
Published: 2026-07-14T20:39:05.532Z
Updated: 2026-07-15T14:26:01.060Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-48815 |
vulnerable | 2026-07-29 00:55:01.665799 |
sigstore-js: `certificateOIDs` verification constraints are silently dropped and never enforced
HIGH (7.5)
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.
Published: 2026-07-14T20:27:16.925Z
Updated: 2026-07-15T12:56:29.848Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-48758 |
vulnerable | 2026-07-29 00:55:01.611363 |
sigstore-js: DSSE payloadType type-binding failure
MEDIUM (5.4)
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.
Published: 2026-07-14T20:36:28.641Z
Updated: 2026-07-15T12:54:55.445Z Reference links |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.