[🐸 Frogbot] Update version of github.com/ulikunitz/xz to 0.5.15

[github-actions]

📦 Vulnerable Dependencies

Severity	ID	Contextual Analysis	Direct Dependencies	Impacted Dependency	Fixed Versions
Medium	CVE-2025-58058	Not Covered	github.com/jfrog/archiver/v3:v3.6.1 github.com/jfrog/jfrog-cli-core/v2:v2.59.5 github.com/jfrog/jfrog-client-go:v1.54.5 github.com/ulikunitz/xz:v0.5.12	github.com/ulikunitz/xz v0.5.12	[0.5.15]

🔖 Details

Vulnerability Details

Contextual Analysis:	Not Covered
Direct Dependencies:	github.com/jfrog/archiver/v3:v3.6.1, github.com/jfrog/jfrog-cli-core/v2:v2.59.5, github.com/jfrog/jfrog-client-go:v1.54.5, github.com/ulikunitz/xz:v0.5.12
Impacted Dependency:	github.com/ulikunitz/xz:v0.5.12
Fixed Versions:	[0.5.15]
CVSS V3:	5.3

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 allocation has already been done. This issue has been patched in version 0.5.14.

---

🐸 JFrog Frogbot

[github-actions]

Unit Tests Results

182 tests  ±0   182 ✅ ±0   0s ⏱️ ±0s
 25 suites ±0     0 💤 ±0 
  1 files   ±0     0 ❌ ±0 

Results for commit 22ee8b5. ± Comparison against base commit 1c135de.