CVE-2024-53267Public exploit

Verification bypass via mismatched transparency-log entry

Published Nov 26, 2024 · Updated Nov 26, 2024

Improper signature verification in Sigstore sigstore-java 1.0.0 allows local users to falsely validate transparency-log inclusion. KeylessVerifier.verify accepts an unrelated but time-correct Rekor entry because it checks the entry without reconstructing it from the artifact digest, certificate, and bundle signature. The artifact signature must remain valid and the signer identity remains visible, but a compromised identity can conceal the signing event from Rekor monitors.

CVSS severity5.5
Medium
EPSS probability0.10%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper signature verification in Sigstore sigstore-java 1.0.0 allows local users to falsely validate transparency-log inclusion. KeylessVerifier.verify accepts an unrelated but time-correct Rekor entry because it checks the entry without reconstructing it from the artifact digest, certificate, and bundle signature. The artifact signature must remain valid and the signer identity remains visible, but a compromised identity can conceal the signing event from Rekor monitors.

The record

CVE
CVE-2024-53267
Published
Nov 26, 2024
Updated
Nov 26, 2024
Vendor
Sigstore
Product
sigstore-java
Classifications
CWE-347, T1553.002
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Nov 26, 2024CVE publishedPublication date reported by the CVE source.
  2. Nov 26, 2024Record 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.

  1. Affected versionversion=>= 1.0.0, < 1.1.0
  2. Affected versionversion=1.0.0 <1.1.0

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

Sigstore · sigstore-javaversion=>= 1.0.0, < 1.1.0; version=1.0.0 <1.1.0

Published CVSS scores

5.5GitHubCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-347Improper Verification of Cryptographic Signature
T1553.002Code Signing

Public exploit references

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