CVE-2025-9396: ckolivas lrzip · NULL Pointer Dereference
Affects ckolivas lrzipSource CVE Database V5
Not known to be exploited · CVSS 4.8 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 24 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ckolivas lrzip | Affected
| Fixed in– |
AI-suggested
To mitigate this vulnerability, European organizations should: 1) Immediately update lrzip to a patched version once available from the vendor or community repositories. 2) Restrict local access to systems running lrzip to trusted users only, employing strict access controls and user privilege management to prevent unauthorized local exploitation. 3) Implement application whitelisting and monitoring to detect abnormal crashes or repeated failures of lrzip processes, which could indicate exploitation attempts. 4) Consider replacing lrzip with alternative compression tools that do not exhibit this vulnerability, especially in high-security environments. 5) Incorporate this vulnerability into local vulnerability management and incident response plans to ensure timely detection and remediation.
Description
A security flaw has been discovered in ckolivas lrzip up to 0.651. This impacts the function __GI_____strtol_l_internal of the file strtol_l.c. Performing manipulation results in null pointer dereference. The attack is only possible with local access. The exploit has been released to the public and may be exploited.