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.
CVE-2026-48816
MEDIUMPre-NVD 6.56.5—Elevated
EchelonGraph scoreMEDIUM confidence
This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 95% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(medium)
- EG Risk
- 45(Track)EG Risk 45/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity65% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 2.5%
- KEV
- Not listed
Published
July 1, 2026
Last Modified
July 15, 2026
Advisory Details (3)
Auto-updated Jul 15, 2026🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github.
github Patch Available🟡 PoC Available
Insufficient Verification of Data Authenticity in sigstore-js · Advisory · sigstore/sigstore-js · GitHub
https://github.com/sigstore/sigstore-js/security/advisories/GHSA-xgjw-pm74-86q4github_pr Patch Available
Require inclusion promise in Rekor entry when used as timestamp source
Patch available: sigstore/sigstore-js @sigstore/mock@0.12.1 (PR #1659 merged 2026-05-22)
https://github.com/sigstore/sigstore-js/pull/1659github_commit Patch Available
commit f074710a91ea (sigstore/sigstore-js)
Patch available: sigstore/sigstore-js @sigstore/mock@0.12.1 (contains commit f074710a91ea)
https://github.com/sigstore/sigstore-js/commit/f074710a91ea9260a9ac2142345634579843a3cdVendor Advisories for CVE-2026-48816(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| @sigstore/verify | 3.1.0 | 3.1.1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 12× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:18 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-01 20:02 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-345
Frequently asked(5)
What is CVE-2026-48816?
CVE-2026-48816 is a medium vulnerability published on July 1, 2026. 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…
When was CVE-2026-48816 disclosed?
CVE-2026-48816 was first published in the National Vulnerability Database on July 1, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48816 actively exploited?
CVE-2026-48816 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-48816?
CVE-2026-48816 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-48816?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48816, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-48816
Is Your Infrastructure Affected by CVE-2026-48816?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.