Artifact trust bypass via unbound log timestamp
Published Jul 14, 2026 · Updated Jul 14, 2026
Improper timestamp verification in Sigstore sigstore-js before 3.1.1 allows attackers to influence trust decisions via a crafted bundle. The @sigstore/verify bundle path treats tlogEntries[].integratedTime as trusted for v0.2 inclusionProof-only entries although the proof does not bind that value. Reachability requires an application to accept an untrusted bundle and rely on transparency-log time for certificate validity or timestampThreshold checks.
Summary
What happened
Improper timestamp verification in Sigstore sigstore-js before 3.1.1 allows attackers to influence trust decisions via a crafted bundle. The @sigstore/verify bundle path treats tlogEntries[].integratedTime as trusted for v0.2 inclusionProof-only entries although the proof does not bind that value. Reachability requires an application to accept an untrusted bundle and rely on transparency-log time for certificate validity or timestampThreshold checks.
The record
- CVE
- CVE-2026-48816
- Published
- Jul 14, 2026
- Updated
- Jul 14, 2026
- Vendor
- Sigstore
- Product
- sigstore-js
- Classifications
- CWE-345, T1553.002
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 14, 2026CVE publishedPublication date reported by the CVE source.
- Jul 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.1.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-xgjw-pm74-86q4 self-contained proof-of-concept harnessproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo