Dev.sigstore:sigstore java: Sigstore Java has a vulnerability with bundle verification of integratedTime (CVE-2026-48791)
A vulnerability in dev.sigstore:sigstore-java version 2.0.0 involves a regression where verification of the integratedTime from Rekor V1 Log Entry against the Fulcio certificate validity was missing. This flaw was introduced by a pull request that removed the check and later fixed in version 2.1.0. The issue allows a malicious actor who has exfiltrated a temporary private key to reuse an old Fulcio certificate without needing direct access to user credentials. The vulnerability only affects version 2.0.0 and was resolved in 2.1.0.
AI Analysis
Technical Summary
The vulnerability in sigstore-java (CVE-2026-48791) is a regression caused by the removal of verification of the integratedTime field from Rekor V1 Log Entry against the Fulcio certificate validity. This verification was erroneously removed in PR #1008 and re-added with enhancements in PR #1185. The issue affects only sigstore-java version 2.0.0 and allows an attacker with access to a user's temporary private key to reuse an old Fulcio certificate, potentially bypassing expected certificate validity checks during bundle verification. The vulnerability is fixed in version 2.1.0.
Potential Impact
The vulnerability impacts users verifying bundles with sigstore-java version 2.0.0. It allows a malicious actor who has exfiltrated the temporary private key used during signing to reuse an old Fulcio certificate without requiring direct access to the user's credentials. This could lead to acceptance of signatures that should be invalid due to certificate validity time constraints. There is no impact on confidentiality or availability, and the severity is rated low.
Mitigation Recommendations
This vulnerability is fixed in dev.sigstore:sigstore-java version 2.1.0. Users should upgrade to version 2.1.0 or later to ensure integratedTime verification is properly enforced. Alternatively, users can re-verify their artifacts using the latest sigstore-java client or another current sigstore client. Auditing transparency logs for unauthorized signatures may also help detect misuse of reused identities. No other immediate action is required if using a fixed version.
Dev.sigstore:sigstore java: Sigstore Java has a vulnerability with bundle verification of integratedTime (CVE-2026-48791)
Description
A vulnerability in dev.sigstore:sigstore-java version 2.0.0 involves a regression where verification of the integratedTime from Rekor V1 Log Entry against the Fulcio certificate validity was missing. This flaw was introduced by a pull request that removed the check and later fixed in version 2.1.0. The issue allows a malicious actor who has exfiltrated a temporary private key to reuse an old Fulcio certificate without needing direct access to user credentials. The vulnerability only affects version 2.0.0 and was resolved in 2.1.0.
CVSS v3.1
Score 2.0low
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in sigstore-java (CVE-2026-48791) is a regression caused by the removal of verification of the integratedTime field from Rekor V1 Log Entry against the Fulcio certificate validity. This verification was erroneously removed in PR #1008 and re-added with enhancements in PR #1185. The issue affects only sigstore-java version 2.0.0 and allows an attacker with access to a user's temporary private key to reuse an old Fulcio certificate, potentially bypassing expected certificate validity checks during bundle verification. The vulnerability is fixed in version 2.1.0.
Potential Impact
The vulnerability impacts users verifying bundles with sigstore-java version 2.0.0. It allows a malicious actor who has exfiltrated the temporary private key used during signing to reuse an old Fulcio certificate without requiring direct access to the user's credentials. This could lead to acceptance of signatures that should be invalid due to certificate validity time constraints. There is no impact on confidentiality or availability, and the severity is rated low.
Mitigation Recommendations
This vulnerability is fixed in dev.sigstore:sigstore-java version 2.1.0. Users should upgrade to version 2.1.0 or later to ensure integratedTime verification is properly enforced. Alternatively, users can re-verify their artifacts using the latest sigstore-java client or another current sigstore client. Auditing transparency logs for unauthorized signatures may also help detect misuse of reused identities. No other immediate action is required if using a fixed version.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-qqw8-7c2r-jxch
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-48791"]
- Ecosystems
- ["Maven"]
- Database Specific Severity
- LOW
- Cvss Version
- 3.1
Threat ID: 6a4452e927e9c797198e1a93
Added to database: 06/30/2026, 23:36:09 UTC
Last enriched: 06/30/2026, 23:52:12 UTC
Last updated: 07/31/2026, 12:27:30 UTC
Views: 61
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
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
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.