CVE-2023-47122Network attack vector

Forged-signature trust via unauthenticated Rekor public keys

Published Nov 10, 2023 · Updated Sep 3, 2024

Improper signature verification in Sigstore Gitsign 0.6.0 through releases before 0.8.0 allows attackers to make forged signatures appear trusted. The rekorPubsFromClient function in pkg/rekor/rekor.go fetched a key payload from the configured Rekor API and added it as an active transparency-log key without TUF authentication. Exploitation requires control of that Rekor server and user interaction during verification; no compromise of the default public instance was known.

CVSS severity4.2
Medium
EPSS probability0.37%
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 Gitsign 0.6.0 through releases before 0.8.0 allows attackers to make forged signatures appear trusted. The rekorPubsFromClient function in pkg/rekor/rekor.go fetched a key payload from the configured Rekor API and added it as an active transparency-log key without TUF authentication. Exploitation requires control of that Rekor server and user interaction during verification; no compromise of the default public instance was known.

The record

CVE
CVE-2023-47122
Published
Nov 10, 2023
Updated
Sep 3, 2024
Vendor
Sigstore
Product
Gitsign
Classifications
CWE-347, T1553.006
Attack vector
network
Privileges
admin

Timeline

How it unfolded

  1. Nov 10, 2023CVE publishedPublication date reported by the CVE source.
  2. Sep 3, 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.6.0, < 0.8.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesadmin

What is affected?

Sigstore · Gitsignversion=>= 0.6.0, < 0.8.0

Published CVSS scores

5.3NIST NVDCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N
4.2GitHub, Inc.CVSS:3.1/AV:N/AC:H/PR:H/UI:R/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)
Vectornetwork
Privilegesadmin
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-347Improper Verification of Cryptographic Signature
T1553.006Code Signing Policy Modification

Public exploit references

No public exploit references are available in this record.

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