CVE-2025-50739

9.8 CRITICAL

📋 TL;DR

CVE-2025-50739 is a critical remote code execution vulnerability in iib0011 omni-tools v0.4.0 caused by unsafe JSON deserialization. Attackers can execute arbitrary code on affected systems by sending malicious JSON payloads. Any system running the vulnerable version is at risk.

💻 Affected Systems

Products:
  • iib0011 omni-tools
Versions: v0.4.0
Operating Systems: All platforms where omni-tools runs
Default Config Vulnerable: ⚠️ Yes
Notes: Any system using the vulnerable JSON deserialization functionality is affected regardless of configuration.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

Full system compromise allowing attackers to execute arbitrary commands, steal data, install malware, or pivot to other systems.

🟠

Likely Case

Remote code execution leading to data exfiltration, ransomware deployment, or system takeover.

🟢

If Mitigated

Limited impact if proper input validation and deserialization controls are implemented.

🌐 Internet-Facing: HIGH - Remote exploitation without authentication makes internet-facing instances extremely vulnerable.
🏢 Internal Only: HIGH - Even internal systems are vulnerable to network-based attacks from compromised internal hosts.

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Public proof-of-concept exists in the GitHub reference. Exploitation requires sending malicious JSON to vulnerable endpoints.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://omnitools.app/json/stringify

Restart Required: No

Instructions:

1. Check for updated version from vendor. 2. If patch available, upgrade immediately. 3. Test functionality after upgrade.

🔧 Temporary Workarounds

Disable vulnerable JSON endpoints

all

Remove or disable JSON processing endpoints that use unsafe deserialization.

# Configuration dependent - modify application config to disable vulnerable endpoints

Implement input validation

all

Add strict input validation and sanitization for all JSON inputs.

# Application code modification required

🧯 If You Can't Patch

  • Network segmentation - isolate affected systems from untrusted networks
  • Implement strict firewall rules to limit access to vulnerable endpoints

🔍 How to Verify

Check if Vulnerable:

Check if running omni-tools v0.4.0 and review code for unsafe JSON deserialization patterns.

Check Version:

# Check omni-tools version: omni-tools --version or check package manager

Verify Fix Applied:

Verify version is updated beyond v0.4.0 and test JSON endpoints with safe payloads.

📡 Detection & Monitoring

Log Indicators:

  • Unusual JSON payloads in application logs
  • Unexpected process execution
  • Error messages related to JSON parsing

Network Indicators:

  • Unusual JSON traffic to omni-tools endpoints
  • Large or malformed JSON payloads

SIEM Query:

source="omni-tools" AND (json_parse_error OR suspicious_payload)

🔗 References

📤 Share & Export