Incorrect Behavior Order: Validate Before Canonicalize Affecting steampipe package, versions <2.4.2-r4
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-CHAINGUARDLATEST-STEAMPIPE-16688848
- published14 May 2026
- disclosed27 May 2026
Introduced: 14 May 2026
NewCVE-2026-45022 (opens in a new tab)How to fix?
Upgrade Chainguard steampipe to version 2.4.2-r4 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream steampipe package and not the steampipe package as distributed by Chainguard.
See How to fix? for Chainguard relevant fixed versions and status.
go-git is an extensible git implementation library written in pure Go. Prior to 5.19.0 and 6.0.0-alpha.3, go-git may parse malformed Git objects in a way that differs from upstream Git. When commit or tag objects contain ambiguous or malformed headers, go-git’s decoded representation may expose values differently from how Git itself would interpret or reject the same object. Additionally, go-git’s commit signing and verification logic operates over commit data reconstructed from go-git’s parsed representation rather than the original raw object bytes. As a result, go-git may sign or verify a commit payload that is not byte-for-byte equivalent to the object stored in the repository. This can cause a signature to appear valid for a commit whose displayed or effective metadata differs from the object that was intended to be signed. This vulnerability is fixed in 5.19.0 and 6.0.0-alpha.3.