Security readout for executives and security teams
Plain-English summary
CVE-2025-15570 affects lrzip, a compression utility, up to version 0.651. A memory use-after-free can be triggered locally in LZMA decompression. The reported impact is limited but includes possible confidentiality, integrity, and availability effects. A public proof of concept exists, but the provided sources do not show active exploitation.
Executive priority
Treat as a moderate operational risk. Prioritize systems that process untrusted archives or allow local multi-user access. The public proof of concept raises urgency, but the local-access requirement and lack of confirmed active exploitation reduce immediate enterprise-wide emergency priority.
Technical view
The flaw is in ckolivas lrzip stream.c, function lzma_decompress_buf. VulDB describes a use-after-free/memory corruption condition, mapped to CWE-416 and CWE-119. CVSS is 5.3 with local access, low complexity, low privileges, and no user interaction. The upstream project was reportedly notified via GitHub issue and had not responded at publication.
Likely exposure
Exposure is most likely on Linux or Unix systems where lrzip 0.651 or earlier is installed and used by local users, scripts, or file-processing workflows. Risk increases if untrusted compressed files are processed on shared servers, build systems, or automated ingestion pipelines.
Exploitation context
Sources state local access is required and public exploit material exists. There is no KEV listing and no cited evidence of active exploitation. The vulnerability is not described as remotely reachable unless lrzip is embedded in a service or automation that processes attacker-supplied files.
Researcher notes
Evidence is limited to CVE/VulDB records, a GitHub issue, public PoC attachment, project repository, and a Debian LTS advisory link. Do not assume a universal upstream fix from the provided data. Validate distribution-specific status before declaring systems remediated.
Mitigation direction
- Inventory systems for lrzip and identify versions at or below 0.651.
- Check upstream and operating system vendor advisories for fixed packages or guidance.
- Review the referenced Debian LTS advisory if using Debian-packaged lrzip.
- Avoid processing untrusted lrzip archives until remediation guidance is applied.
- Limit lrzip execution to trusted users and controlled workflows.
Validation and detection
- Confirm installed lrzip versions on servers, workstations, containers, and build images.
- Identify scripts or services that invoke lrzip on user-supplied files.
- Verify whether package managers provide an updated lrzip build.
- Track the upstream GitHub issue for maintainer response or patch status.
- Document compensating controls where lrzip cannot be removed or updated.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-119: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-15570 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
4 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R1.83.4VulDBCVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R1.83.4VulDBCVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P——VulDBAV:L/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR3.16.4VulDBVulnerability scoring details
Base CVSS 4.0 score
4.8MediumVector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R
Base CVSS 3.0 score
5.3MediumVector: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R
Base CVSS 2.0 score
4.3MediumVector: AV:L/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timelineVulDB
Advisory disclosed
- Source timelineVulDB
VulDB entry created
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- Source timelineVulDB
VulDB entry last update
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- VDB-344926 | ckolivas lrzip stream.c lzma_decompress_buf use after freeCVE reference, VulDB · vdb-entry, technical-description
- VDB-344926 | CTI Indicators (IOB, IOC, IOA)CVE reference, VulDB · signature, permissions-required
- Submit #752595 | ckolivas lrzip 0.651 Memory CorruptionCVE reference, VulDB · third-party-advisory
- https://github.com/ckolivas/lrzip/issues/262CVE reference, VulDB · issue-tracking
- https://github.com/user-attachments/files/21709004/PoC_UAF.zipCVE reference, VulDB · exploit
- https://github.com/ckolivas/lrzip/CVE reference, VulDB · product
- https://lists.debian.org/debian-lts-announce/2026/05/msg00011.htmlCVE reference, CVE
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Restriction of Operations within the Bounds of a Memory Buffer
Improper Restriction of Operations within the Bounds of a Memory Buffer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.