GHSA-jc7w-c686-c4v9

Memory leaks when decoding a corrupted multiple LZMA archives in github.com/ulikunitz/xz

Medium highest severity reported · also known as CVE-2025-58058, GO-2025-3922

catalog tools match this advisory

ship the vulnerable code in their release binary (Go tools analyzed with govulncheck)

in the CISA KEV catalog

0.4%

EPSS for CVE-2025-58058, percentile 38

Catalog tools matching GHSA-jc7w-c686-c4v9

Tool	Version scanned	Package	Fixed in	Released binary	Declared in or found in	Dispute
bearer Static Application Security Testing (SAST) › Multi-language	v2.1.3	`github.com/ulikunitz/xz@v0.5.14` golang	v0.5.15	vulnerable code in binary	`bearer` (release binary; govulncheck only)	Dispute
gitleaks Pre-commit & Secrets Detection	v8.30.1	`github.com/ulikunitz/xz@v0.5.12` golang	0.5.15	module in binary	`go.mod`	Dispute
dockle Container Security › Image Scanning	v0.4.15	`github.com/ulikunitz/xz@v0.5.12` golang	0.5.15	module in binary	`go.mod`	Dispute

Vulnerabilities are known advisories that Grype matches against the dependencies declared in each project's release source (manifests and lockfiles, including development and build dependencies). A match does not mean the tool is exploitable: the vulnerable code may be unused, test-only, or not shipped in the released binary. KEV: listed in the CISA Known Exploited Vulnerabilities catalog. EPSS: FIRST's estimated probability of exploitation in the next 30 days. Both describe the vulnerability in general, not its exploitability through this tool; a match in a workflow file refers to a GitHub Action, not to shipped code. Released binary is only analyzed for Go tools with a Linux release binary; other tools show not analyzed.

Advisory sources

GitHub advisory GHSA-jc7w-c686-c4v9 · NVD CVE-2025-58058 · Go vulnerability GO-2025-3922 · OSV GHSA-jc7w-c686-c4v9

Grype data sources: https://github.com/advisories/GHSA-jc7w-c686-c4v9 · https://pkg.go.dev/vuln/GO-2025-3922