CVE-2026-45022Network attack vector

Signature validation bypass via reconstructed Git objects

Published May 27, 2026 · Updated May 27, 2026

Object verification in go-git before 5.19.0 and 6.0.0-alpha.1 through 6.0.0-alpha.2 allows remote authenticated users to trust altered metadata. The commit and tag parsers accept ambiguous or malformed headers, while signing and verification reconstruct parsed data instead of using the stored raw object bytes. Exploitation requires attacker-controlled Git objects to reach a signing or verification workflow, causing a valid signature to cover metadata different from the stored commit.

CVSS severity7.0
High
EPSS probability0.16%
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

Object verification in go-git before 5.19.0 and 6.0.0-alpha.1 through 6.0.0-alpha.2 allows remote authenticated users to trust altered metadata. The commit and tag parsers accept ambiguous or malformed headers, while signing and verification reconstruct parsed data instead of using the stored raw object bytes. Exploitation requires attacker-controlled Git objects to reach a signing or verification workflow, causing a valid signature to cover metadata different from the stored commit.

The record

CVE
CVE-2026-45022
Published
May 27, 2026
Updated
May 27, 2026
Vendor
go-git
Product
go-git
Classifications
CWE-180, CWE-345, T1553.002
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. May 27, 2026CVE publishedPublication date reported by the CVE source.
  2. May 27, 2026Record 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=< 5.19.0
  2. Affected versionversion=>= 6.0.0-alpha.1, < 6.0.0-alpha.3

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

go-git · go-gitversion=< 5.19.0; version=>= 6.0.0-alpha.1, < 6.0.0-alpha.3

Published CVSS scores

7.0GitHub, Inc.CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N
7.5NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/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)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-180Incorrect Behavior Order: Validate Before Canonicalize
CWE-345Insufficient Verification of Data Authenticity
T1553.002Subvert Trust Controls: Code Signing

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