CVE-2026-48791
LOWDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:N/I:L/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 0% of all known CVEs.
References
Related Vulnerabilities
Other CWE-347 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2018-16042 | Medium | 6.5 | 82% | - | - |
| CVE-2025-59718 | Critical | 9.8 | 69% | KEV | Fix |
| CVE-2025-25292 | Critical | 9.8 | 65% | - | Fix |
| CVE-2021-22160 | Critical | 9.8 | 53% | - | Fix |
| CVE-2013-3900 | Medium | 5.5 | 45% | KEV | - |
| CVE-2018-0114 | High | 7.5 | 43% | - | Fix |
Common questions
How do I fix CVE-2026-48791?
No published fix for CVE-2026-48791 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-48791 being actively exploited?
Not that we know of. CVE-2026-48791 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.06% is the estimated probability that it will be exploited in the next 30 days. That is higher than 0% of all scored CVEs.
How severe is CVE-2026-48791?
CVE-2026-48791 has a CVSS v3 base score of 2.0, rated low. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-48791
Markdown
[](https://tridentstack.com/cve/CVE-2026-48791)HTML
<a href="https://tridentstack.com/cve/CVE-2026-48791"><img src="https://tridentstack.com/cve/badge/CVE-2026-48791.svg" alt="CVE-2026-48791"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-13.