Vulnerability · CVE-2025-58058
xz is a pure golang package for reading and writing xz-compressed files.
Published Aug 28, 2025 · catalog updated Aug 29, 2025 · xz is a pure
Last checked Oct 29, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2025-58058. EPSS is 0.43%. Act only if a listed version of xz is a pure is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (xz is a pure).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2026-34743 · Low
- Severity
- Medium5.3
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.43%
- Remediation
- Version ranges on file
- Affected products
- vendor ulikunitz xz < 0.5.14
xz is a pure golang package for reading and writing xz-compressed files. Prior to version 0.5.14, it is possible to put data in front of an LZMA-encoded byte stream without detecting the situation while reading the header. This can lead to increased memory consumption because the current implementation allocates the full decoding buffer directly after reading the header. The LZMA header doesn't include a magic number or has a checksum to detect such an issue according to the specification. Note that the code recognizes the issue later while reading the stream, but at this time the memory alloc
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- vendor ulikunitz xz < 0.5.14< 0.5.14
How to fix CVE-2025-58058
Upgrade
CVE-2025-58058 lists a fix boundary at 0.5.14. Compare the installed build with that boundary before you change production.
Version check
Affected < 0.5.14
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2025-58058. EPSS is 0.43%. Act only if a listed version of xz is a pure is installed.
Which versions are affected?
Compare what you have installed with ulikunitz xz < 0.5.14 < 0.5.14. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.43%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Aug 28, 2025 · EUVD
Detected
xz is a pure golang package for reading and writing xz-compressed files. Prior to version 0.5.14, it is possible to put data in front of an LZMA-encoded byte stream without detecting the situation while reading the header. This can lead to increased memory consumption because the current implementation allocates the full decoding buffer directly after reading the header. The LZMA header doesn't in
Aug 29, 2025 · EUVD
Updated
xz is a pure golang package for reading and writing xz-compressed files. Prior to version 0.5.14, it is possible to put data in front of an LZMA-encoded byte stream without detecting the situation while reading the header. This can lead to increased memory consumption because the current implementation allocates the full decoding buffer directly after reading the header. The LZMA header doesn't in
Sources
- CVE.orgVulnerability recordCVE-2025-58058
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2025-58058
30-day exploitation probability 0.43%
first.org - EUVDVulnerability recordEUVD-2025-26149
xz is a pure golang package for reading and writing xz-compressed files. Prior to version 0.5.14, it is possible to put data in front of an LZMA-encoded byte stream without detecting the situation while reading the header. This can lead to increased memory consumption because the
euvd.enisa.europa.eu
References
Freshness
Last verified in this catalog Oct 29, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- FIRST EPSSOct 23, 2026
- CVE.orgOct 22, 2026
- EUVDOct 22, 2026