cve.bz

CVE-2026-48791 sigstore sigstore-java

2.0 lowEPSS 0.07%Fix available

Low (2.0) in sigstore sigstore-java. EPSS 0.07% estimated probability of exploitation activity in the next 30 days. Fixed in dev.sigstore:sigstore-java 2.1.0.

On this page
sigstore-java is a sigstore java client for interacting with sigstore infrastructure. Version 2.0.0 erroneously removed verification of the integrated (Rekor entry) time) against the Fulcio certificate. Version 2.1.0 re-added this verification with enhancements that adhere to the Sigstore verification spec. The old sigstore-conformance test for this check was built incorrectly. This vulnerability impacts only users verifying bundles with `dev.sigstore:sigstore-java:2.0.0`. Older versions are not affected; it is fixed in `dev.sigstore:sigstore-java:2.1.0` A malicious actor may exploit this if they were able to access a users system and exfiltrate the temporary private key used during signing and then reuse an old fulcio certificate later without requiring direct access to the user's credentials. Users may protect themselves by re-verifying their artifacts using the newest sigstore-java or another current sigstore client. Transparency logs may also be audited for unauthorized signatures for a suspected reused identity.

Severity

CVSS 3.1

2.0 low
CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:N/I:L/A:N
EPSS
0.07% (unchanged from 0.07% a week ago; 0.07% 30 days ago) estimated probability of exploitation activity in the next 30 days; 0th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-08-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-347 Improper Verification of Cryptographic Signature
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • dev.sigstore:sigstore-java (Maven): fixed in 2.1.0

Ask an AI about this CVE

Show the promptExplain CVE-2026-48791 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-48791?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-48791?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-48791 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
sigstore-java= 2.0.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-qqw8-7c2r-jxchMavendev.sigstore:sigstore-java>=2.0.0 <2.1.02.1.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu24.04:LTS, 26.04:LTS, 26.10golang-github-sigstore-sigstoreno fix listedUBUNTU-CVE-2026-48791

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu.

Attack patterns (CAPEC)

  • CAPEC-463 Padding Oracle Crypto Attack Severity: High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON