Skip to main content
VulnerabilityPublished Updated

CVE-2025-13566: jarun nnn · Double Free

Affects jarun nnnSource CVE Database V5

0

Not known to be exploited · CVSS 4.8 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 3% 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:X

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubjarun/nnnpkg:github/jarun/nnnOther threatsAffected
  • =5.0
  • =5.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2025-13566, European organizations should: 1) Immediately apply the patch identified by commit 2f07ccdf21e705377862e5f9dfa31e1694979ac7 from the official 'nnn' repository or vendor updates. 2) Restrict local access to systems running 'nnn' to trusted users only, minimizing the risk of local exploitation. 3) Implement strict user privilege management and monitor for unusual local activity that could indicate exploitation attempts. 4) Employ memory protection mechanisms such as Address Space Layout Randomization (ASLR) and stack canaries to reduce exploitation success. 5) Regularly audit installed software versions and remove or replace unused or unnecessary tools like 'nnn' in sensitive environments. 6) Educate users about the risks of running untrusted commands or plugins within 'nnn' to avoid triggering the vulnerable code paths. 7) Integrate vulnerability scanning and patch management processes to ensure timely updates of open-source tools.

Description

A security vulnerability has been detected in jarun nnn up to 5.1. The impacted element is the function show_content_in_floating_window/run_cmd_as_plugin of the file nnn/src/nnn.c. The manipulation leads to double free. An attack has to be approached locally. The identifier of the patch is 2f07ccdf21e705377862e5f9dfa31e1694979ac7. It is suggested to install a patch to address this issue.

References

Community reviews

Loading reviews…