Description

A vulnerability was detected in aaronsb memory-graph up to 5cfd2382778837b9f6399080956eee670d00452c. Affected by this vulnerability is the function JsonMemoryStorage.createDomain/JsonMemoryStorage.getMemories/JsonMemoryStorage.saveMemories of the file src/tools/memoryTools.ts. The manipulation results in path traversal. The attack must be initiated from a local position. This product operates on a rolling release basis, ensuring continuous delivery. Consequently, there are no version details for either affected or updated releases. The project was informed of the problem early through an issue report but has not responded yet.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "5.3",
  "pubDate": "2026-08-08T13:17:10.947Z",
  "pubdate": "2026-08-08T13:17:10.947Z",
  "executiveSummary": "A path traversal vulnerability has been identified in the memory-graph repository by aaronsb, specifically affecting the JsonMemoryStorage class within the src/tools/memoryTools.ts file up to commit 5cfd2382778837b9f6399080956eee670d00452c. This security defect arises from insufficient sanitization or validation of user-supplied input utilized in file system operations across the createDomain, getMemories, and saveMemories functions. An attacker capable of executing a local attack vector can manipulate file paths to access, modify, or create files outside the intended storage directory, potentially leading to arbitrary file read and write operations within the context of the running application. Given that the project operates on a rolling release model without explicit version tags, all deployments utilizing commits up to the specified hash are considered vulnerable. The vendor has been notified via an issue report but has not yet provided an official response or patch. The overall risk is localized due to the requirement for a local execution position, but the potential impact on system integrity and confidentiality remains significant depending on the privileges of the host process.",
  "technicalDetails": "The vulnerability resides in the src/tools/memoryTools.ts file of the aaronsb memory-graph project, specifically impacting the JsonMemoryStorage.createDomain, JsonMemoryStorage.getMemories, and JsonMemoryStorage.saveMemories functions. The root cause of the vulnerability is the improper handling and lack of strict canonicalization or validation of input parameters that dictate file paths or domain names used during local storage interactions. Because these functions construct file system paths dynamically by concatenating untrusted input directly with base directory paths, an attacker can supply directory traversal sequences such as dot-dot-slash (../) patterns.\nExploitation of this vulnerability requires local access to the system where the application is executed, indicating that the attacker must either possess local execution privileges or leverage an auxiliary injection vector to influence the input parameters passed to the vulnerable memory storage functions. When a crafted payload containing path traversal sequences is processed by JsonMemoryStorage.createDomain, JsonMemoryStorage.getMemories, or JsonMemoryStorage.saveMemories, the underlying file system APIs resolve the path outside the intended secure boundary of the memory graph storage directory.\nThe attack flow proceeds as follows: First, the attacker identifies or induces an entry point where manipulated domain names or memory identifiers are processed by the storage mechanism. Second, the attacker crafts a malicious input string incorporating directory traversal tokens. Third, the application passes this unsanitized string directly into file system resolution routines within src/tools/memoryTools.ts. Fourth, the file system reads from or writes to the targeted unauthorized file location, depending on which function was invoked. For instance, invoking saveMemories with a traversed path could overwrite critical system or application files, while getMemories could allow the disclosure of sensitive local files readable by the application process.\nThe affected components comprise the commit history up to 5cfd2382778837b9f6399080956eee670d00452c. Due to the rolling release nature of the product, no formal version identifiers exist. There are no specific authentication or network exposure requirements inherent to the vulnerability itself, as the primary constraint is the ability to initiate the attack sequence from a local position interacting with the storage component."
}