CVE-2025-50739: omni-tools · Code Injection
Affects omni-toolsSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 30 Oct 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubfai1424/omni-toolspkg:github/fai1424/omni-toolsOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Immediately restrict network access to omni-tools instances by implementing strict firewall rules and network segmentation to limit exposure to untrusted networks.
- Monitor logs and network traffic for unusual JSON payloads or suspicious activity indicative of exploitation attempts.
- Employ application-layer filtering or web application firewalls (WAFs) capable of detecting and blocking malicious JSON deserialization patterns.
- Conduct thorough asset inventories to identify all deployments of iib0011 omni-tools v0.4.0 within the organization.
- Engage with the vendor or community to obtain patches or updates as soon as they become available and apply them promptly.
- Consider temporary mitigation by disabling or isolating omni-tools functionality if feasible until a patch is released.
- Educate development and operations teams about the risks of unsafe deserialization and promote secure coding practices to prevent similar vulnerabilities.
- Implement endpoint detection and response (EDR) solutions to detect post-exploitation behaviors.
- Prepare incident response plans specific to remote code execution scenarios to enable rapid containment and recovery.
Description
iib0011 omni-tools v0.4.0 is vulnerable to remote code execution via unsafe JSON deserialization.