Description

A weakness has been identified in RightNow-AI OpenFang up to 0.6.9. This vulnerability affects the function shell_exec of the file crates/openfang-runtime/src/tool_runner.rs. This manipulation causes uncontrolled memory allocation. The attack is possible to be carried out remotely. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "4.3",
  "pubDate": "2026-09-03T05:16:47.493Z",
  "pubdate": "2026-09-03T05:16:47.493Z",
  "executiveSummary": "A critical vulnerability exists in RightNow-AI OpenFang versions up to and including 0.6.9, stemming from improper handling of process execution.\nThe vulnerability is classified as uncontrolled memory allocation, which can lead to system instability, resource exhaustion, or denial-of-service (DoS) conditions.\nThe flaw resides within the shell_exec function located in the crates/openfang-runtime/src/tool_runner.rs file.\nThe vulnerability is exploitable remotely, allowing unauthenticated attackers to trigger the flaw without requiring specific user privileges.\nPublicly available exploit code increases the risk profile significantly, and the vendor has remained unresponsive to disclosure attempts.\nOrganizations using OpenFang are at high risk, as the uncontrolled memory growth can crash the runtime environment, potentially impacting dependent services and overall system availability.",
  "technicalDetails": "The root cause of the vulnerability is found in the implementation of the shell_exec function within the crates/openfang-runtime/src/tool_runner.rs source file. The function fails to implement sufficient constraints or validation on the resources requested during execution, specifically regarding memory allocation patterns when invoked through the runtime.\nThe attack flow initiates when an external actor sends a crafted payload to the affected component. By manipulating inputs processed by the shell_exec function, an attacker can induce the runtime to allocate arbitrary amounts of heap memory. Because the system lacks necessary checks or limits on the allocation requests originating from this function, the application process consumes memory uncontrollably until the operating system's kernel invokes the Out-Of-Memory (OOM) killer or the process crashes due to memory exhaustion.\nThe exploitation method leverages the lack of sanitization and resource management within the tool_runner logic. Since shell_exec serves as an interface for system-level operations, the vulnerability allows for a remote attack vector, bypassing the need for local or authenticated access. The process interacts directly with the system shell or underlying environment, and the uncontrolled memory consumption occurs during the spawning or handling of the executed command's output or environment buffer.\nAffected versions include all iterations up to 0.6.9. There are no authentication or privilege requirements to trigger this flaw, as the vulnerable path is reachable via remote network input. The impact is significant: upon successful exploitation, the service becomes unresponsive, leading to a complete denial-of-service for the OpenFang runtime. In some environments, if the memory allocation is performed in a way that impacts the underlying host's virtual memory subsystem, it may lead to wider system degradation beyond the application process itself.\nBecause public exploit code exists, the barrier to entry for attackers is extremely low. The lack of vendor response means there is no official patch currently available to remediate the logic flaw within the crates/openfang-runtime/src/tool_runner.rs file. Security teams must treat the availability of public exploits as a high-priority threat indicator."
}