Skip to content
Fencer Intel
medium 6.5

CVE-2026-48816 json

sigstore-js: Insufficient Verification of Data Authenticity

published 5mo ago modified 18d ago also EUVD-2026-44502 , GHSA-xgjw-pm74-86q4

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.1%
EPSS 0.1% chance of exploitation in 30 days, percentile 3%
public exploits
0
none known

Summary

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.

Patch / fix

  • npm @sigstore/verify 3.1.1

Is CVE-2026-48816 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-48816 updated cvss 6.5

sigstore-js: github.com/sigstore/sigstore-js: sigstore-js: Insufficient verification of data authenticity allows timestamp manipulation

  • Red Hat Enterprise Linux 8 sigstore 3.1.0 Red Hat Enterprise Linux 9 sigstore 3.1.0 Red Hat Enterprise Linux 10 sigstore 3.1.0 Red Hat OpenShift Dev Spaces sigstore 3.1.0 Red Hat Satellite 6 sigstore 3.1.0 Red Hat Self-service automation portal 2 sigstore 3.1.0
    affected: workaround, no fix available “Upgrade to the latest sigstore-js (>= 3.1.1) release that addresses GHSA-xgjw-pm74-86q4.”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
3mo ago

Exploit prediction

0.14% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-11).

Exploits and checks

  • github.com https://github.com/sigstore/sigstore-js/security/advisories/GHSA-xgjw-pm74-86q4 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
npm @sigstore/verify
>=3.1.0, <3.1.1
3.1.1

Affected products

  • sigstore sigstore-js

Classification

Weakness
  • CWE-345 Insufficient Verification of Data Authenticity

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of sigstore/sigstore-js published their own advisory on GitHub. Reviewed sources take precedence over it.