Live › vulnerability › CVE-2024-8551
Go to dashboardAgentScope's save-workflow and load-workflow functions do not restrict file paths, so a crafted name can point outside the intended folder. An attacker can read and overwrite arbitrary JSON files on the host, including configuration files that may hold API keys or passwords.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-26 20:56 UTC, 0h before NVD. All times on this page are UTC.
Teams that run AgentScope 0.1.1 or earlier and expose its save-workflow or load-workflow functions to input they do not fully control. Deployments where only trusted developers call these functions with fixed paths are less exposed. unknown whether the functions are reachable over a network by default.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| agentscope | pypi | <= 0.1.1 | – |
| modelscope agentscope | vendor | – | – |
pip show agentscope and check whether the version is 0.1.1 or lower.agentscope package to a version after 0.1.1 (the fixed version is not stated in the source; check the GHSA advisory).Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
A path traversal vulnerability exists in the save-workflow and load-workflow functionality of modelscope/agentscope versions prior to the fix. This vulnerability allows an attacker to read and write arbitrary JSON files on the filesystem, potentially leading to the exposure or modification of sensitive information such as configuration files, API keys, and hardcoded passwords.
This page as .md · .json · in your agent: get_signal("CVE-2024-8551")
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.