Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The github.com/ulikunitz/xz Go package before 0.5.15 can allocate a large decoding buffer when reading a corrupted LZMA stream, because the LZMA header has no magic number or checksum to detect the problem early. An attacker who can supply LZMA data to a program using lzma.NewReader can cause high memory consumption, which can exhaust memory on servers with limited RAM. Upgrade to version 0.5.15, which limits the dictionary size through ReaderConfig DictCap (default 2^31-1 bytes) and caps it by the file size.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 5.3 | Medium | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0043, the 38th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:14 UTC First seen by agentprime
- 31 Oct 2026, 14:14 UTC Confirmed by OSV