Skip to main content
VulnerabilityPublished

CVE-2025-58176: OpenAgentPlatform Dive · Code Injection

Affects OpenAgentPlatform DiveSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High · fixed in 0.9.4 : patch OpenAgentPlatform Dive soon.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
9.2% chance of exploitation in 30 days – higher than 95% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.9.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Sep 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

AI-suggested

  1. Immediate upgrade to Dive version 0.9.4 or later, which contains the fix for this vulnerability.
  2. Implement strict URL filtering and validation at the network perimeter to block or flag dive: custom URL schemes originating from untrusted or external sources.
  3. Educate users about the risks of clicking on unknown or suspicious links, especially those that may trigger application launches via custom URL handlers.
  4. Employ endpoint protection solutions capable of detecting anomalous process launches or suspicious command executions initiated by Dive or related processes.
  5. For organizations deploying Dive in managed environments, consider disabling or restricting the registration of custom URL handlers unless absolutely necessary.
  6. Monitor logs and network traffic for unusual activity related to Dive or unexpected invocations of the custom URL scheme.
  7. Conduct internal audits to identify all instances of Dive deployment and ensure timely patching.
  8. Use application whitelisting to prevent unauthorized execution of code spawned by Dive.

Description

Dive is an open-source MCP Host Desktop Application that enables integration with function-calling LLMs. In versions 0.9.0 through 0.9.3, there is a one-click Remote Code Execution vulnerability triggered through a custom url value, `transport` in the JSON object. An attacker can exploit the vulnerability in the following two scenarios: a victim visits a malicious website controlled by the attacker and the website redirect to the URL automatically, or a victim clicks on such a crafted link embedded on a legitimate website (e.g., in user-generated content). In both cases, the browser invokes Dive's custom URL handler (dive:), which launches the Dive app and processes the crafted URL, leading to arbitrary code execution on the victim’s machine. This vulnerability is caused by improper processing of custom url. This is fixed in version 0.9.4.

References

Community reviews

Loading reviews…