Read the docs
TI-2024-36256 Aliases CVE-2024-54140GHSA-jp26-88mw-89qr

sigstore-java has a vulnerability with bundle verification

Priority MEDIUM 44CWE-20Published · Updated

Key facts

Attack vector
Local
Privileges required
None
User interaction
None
Attack complexity
Low
Attack requirements
Present
Impact type
—
Confidentiality · integrity · availability
None · Low · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA and GitHub.

Summary

sigstore-java is a sigstore java client for interacting with sigstore infrastructure. sigstore-java has insufficient verification for a situation where a bundle provides a invalid signature for a checkpoint. This bug impacts clients using any variation of KeylessVerifier.verify(). Currently checkpoints are only used to ensure the root hash of an inclusion proof was provided by the log in question. Failing to validate that means a bundle may provide an inclusion proof that doesn't actually correspond to the log in question. This may eventually lead a monitor/witness being unable to detect when a compromised logs are providing different views of themselves to different clients. There are other mechanisms right now that mitigate this, such as the signed entry timestamp. Sigstore-java currently requires a valid signed entry timestamp. By correctly verifying the signed entry timestamp we can make certain assertions about the log signing the log entry (like the log was aware of the artifact signing event and signed it). Therefore the impact on clients that are not monitors/witnesses is very low. This vulnerability is fixed in 1.2.0.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00212 11th percentileScored 2026-11-07
Fix Fixed sigstore-java (sigstore): 1.2.0dev.sigstore:sigstore-java (Maven): 1.2.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
sigstoresigstore-javabefore 1.2.01.2.0Patch availableCNA
—dev.sigstore:sigstore-java (Maven)before 1.2.01.2.0Patch availableGHSA-jp26-88mw-89qr
  • sigstore-java Vendorsigstore Affected before 1.2.0 Fixed in 1.2.0 Patch available CNA
  • dev.sigstore:sigstore-java (Maven) Vendor— Affected before 1.2.0 Fixed in 1.2.0 Patch available GHSA-jp26-88mw-89qr

CPE names CISA-ADP · 1

CPEVersionsRoleVendor
cpe:2.3:a:sigstore:sigstore-java:*:*:*:*:*:*:*:*——sigstore
  • cpe:2.3:a:sigstore:sigstore-java:*:*:*:*:*:*:*:* Versions — — ·sigstore

Remediation

  • Fix · CNA sigstore-java (sigstore) Fixed in 1.2.0
  • Fix · GHSA-jp26-88mw-89qr dev.sigstore:sigstore-java (Maven) Fixed in 1.2.0 Advisory →

Timeline

  1. 2026-10-02 Threatist record created from CVE-2024-54140
  2. 2026-10-03 Alias added: GHSA-jp26-88mw-89qr

References

Advisory 1

Other 4

  • TI-2022-16356 False positive signature verification in cosign CVSS 3.1CRITICAL 9.8
  • TI-2026-36084 sigstore-js: `certificateOIDs` verification constraints are silently dropped and never enforced CVSS 3.1HIGH 7.5
  • TI-2024-19670 Cosign vulnerable to machine-wide denial of service via malicious artifacts CVSS 3.1HIGH 7.5
  • TI-2026-18290 Fulcio vulnerable to Server-Side Request Forgery (SSRF) via MetaIssuer Regex Bypass CVSS 3.1MEDIUM 5.8
  • TI-2026-36085 sigstore-js: Insufficient Verification of Data Authenticity CVSS 3.1MEDIUM 6.5
  • TI-2024-19669 Cosign vulnerable to system-wide denial of service via malicious attachments CVSS 3.1MEDIUM 5.9
See all 39 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences