CVE-2024-51746Public exploit

Commit integrity bypass via unmatched Rekor entry

Published Nov 5, 2024 · Updated Nov 5, 2024

Improper verification in Sigstore Gitsign before 0.11.0 allows local users to validate the wrong commit payload through an unrelated Rekor entry. The online verifier treats Rekor search results as matching both the public key and payload, then omits a hash comparison against the payload under review. Exploitation requires the signing-key holder to reuse a cached certificate, win response ordering, and act within its 10-minute validity window; certificate identity remains checked.

CVSS severity1.8
Low
EPSS probability0.12%
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 verification in Sigstore Gitsign before 0.11.0 allows local users to validate the wrong commit payload through an unrelated Rekor entry. The online verifier treats Rekor search results as matching both the public key and payload, then omits a hash comparison against the payload under review. Exploitation requires the signing-key holder to reuse a cached certificate, win response ordering, and act within its 10-minute validity window; certificate identity remains checked.

The record

CVE
CVE-2024-51746
Published
Nov 5, 2024
Updated
Nov 5, 2024
Vendor
Sigstore
Product
Gitsign
Classifications
CWE-706, T1553
Attack vector
local
Privileges
unauthenticated

Timeline

How it unfolded

  1. Nov 5, 2024CVE publishedPublication date reported by the CVE source.
  2. Nov 5, 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=0 <0.11.0
  2. Affected versionversion=< 0.11.0

What conditions does exploitation require?

Attack vectorlocal
Required privilegesunauthenticated

What is affected?

Sigstore · Gitsignversion=0 <0.11.0; version=< 0.11.0

Published CVSS scores

1.8GitHub, Inc.CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA: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
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-706Use of Incorrectly-Resolved Name or Reference
T1553Subvert Trust Controls

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