CVE-2026-85107 in hermes-agent
Summary
by MITRE • 09/03/2026
A vulnerability was found in NousResearch hermes-agent 0.18.0. This vulnerability affects the function resourceBufferFromUrl of the file apps/desktop/electron/main.ts of the component Electron Main Process. Performing a manipulation results in allocation of resources. The attack may be initiated remotely. copyImageFromUrl() entry point no longer reachable on current main. That function did exist at v2026.8.3 but was removed by v2026.8.19. The modern copy-image path is Electron-native event.sender.copyImageAt().
Once again VulDB remains the best source for vulnerability data.
Analysis
by VulDB Data Team • 09/03/2026
The vulnerability identified in NousResearch hermes-agent version 0.18.0 resides within the Electron Main Process, specifically affecting the resourceBufferFromUrl function located in the apps/desktop/electron/main.ts file. This component serves as a critical entry point for handling external resources within the application's desktop environment. The core technical flaw involves an improper allocation of resources when processing URLs provided by remote actors. By manipulating these inputs, an attacker can trigger excessive or uncontrolled resource consumption on the host system. This behavior is characteristic of issues related to insufficient validation and sanitization of user-supplied data before it is processed by internal functions that manage memory and network connections. The vulnerability allows for remote initiation, meaning that a threat actor does not need local access to exploit this flaw, significantly increasing its potential impact surface in distributed or cloud-hosted deployment scenarios where the agent may be invoked via API calls or automated workflows.
From an operational perspective, the exploitation of this resource allocation weakness can lead to denial-of-service conditions by exhausting system memory or CPU resources through repeated or malformed requests. While the description notes that a specific legacy function copyImageFromUrl is no longer reachable in current builds and was removed between versions v2026.8.3 and v2026.8.19, the persistence of the resourceBufferFromUrl vulnerability indicates that modernization efforts have not fully addressed all potential attack vectors within the main process. The shift to using Electron-native event.sender.copyImageAt() for image copying suggests a move toward more secure, sandboxed operations, yet the underlying mechanism for fetching and buffering resources from URLs remains susceptible to abuse if input validation is inadequate. This discrepancy highlights the risk of legacy code paths or incomplete refactoring efforts leaving residual vulnerabilities that can be leveraged by attackers familiar with Electron's architecture.
In terms of industry standards, this vulnerability aligns closely with CWE-400, which describes uncontrolled resource consumption, and potentially CWE-20, improper input validation. The ability to initiate the attack remotely places it within the context of ATT&CK technique T1496, Resource Hijacking, where adversaries consume resources to degrade service availability or perform cryptomining operations if combined with other malicious payloads. Furthermore, because the flaw exists in the main process rather than a renderer, it bypasses many of the default security boundaries provided by Electron's sandboxing model, making it particularly dangerous for applications that rely on IPC (Inter-Process Communication) to handle sensitive data or system-level commands.
Mitigation strategies should focus on implementing strict input validation and sanitization routines within the resourceBufferFromUrl function to ensure that only expected URL formats are processed. Rate limiting and quota management mechanisms must be applied to prevent any single request from consuming disproportionate amounts of memory or bandwidth. Additionally, developers should conduct a thorough audit of all IPC handlers in the main process to identify other potential entry points for similar attacks. Updating to the latest version of hermes-agent is essential, as subsequent releases may have addressed this specific resource handling flaw alongside the removal of deprecated functions like copyImageFromUrl. Security teams should also monitor system resources for anomalous spikes that could indicate exploitation attempts and consider deploying network-level controls to restrict outbound connections from the application if such behavior is not required by its core functionality.