VulnerabilityPublished 4 Nov 2024Updated 6 Nov 2024

CVE-2024-48050: agentscope · Code Injection

Affects agentscopeSource CVE Database V5

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score

9.8Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.8% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
PyPIagentscope`pkg:pypi/agentscope`Other threats	Affected <=0.0.4	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-48050, organizations should immediately audit their use of agentscope and identify any deployments running versions up to 0.0.4. Until an official patch is released, the following specific actions are recommended: 1) Disable or restrict access to the vulnerable is_callable_expression function or the affected workflow_utils.py module to prevent processing of untrusted input; 2) Implement input validation and sanitization to ensure that any input passed to eval() or similar functions is strictly controlled or avoided; 3) Replace the use of eval() with safer alternatives such as ast.literal_eval() if only literals need to be parsed; 4) Employ runtime application self-protection (RASP) or web application firewalls (WAFs) to detect and block suspicious payloads targeting this vulnerability; 5) Monitor logs and network traffic for anomalous activity indicative of exploitation attempts; 6) Plan for an immediate upgrade to a patched version once available; 7) Conduct code reviews and security testing to identify and remediate similar unsafe coding patterns elsewhere in the codebase.

Description

In agentscope <=v0.0.4, the file agentscope\web\workstation\workflow_utils.py has the function is_callable_expression. Within this function, the line result = eval(s) poses a security risk as it can directly execute user-provided commands.

Impact

The impact of CVE-2024-48050 is severe for organizations using affected versions of agentscope. Successful exploitation allows remote attackers to execute arbitrary code with the privileges of the agentscope process, potentially leading to full system compromise. This can result in unauthorized data access, data modification or deletion, installation of persistent malware, lateral movement within networks, and disruption of services. Because the vulnerability requires no authentication and no user interaction, it can be exploited at scale by automated attacks, increasing the risk of widespread damage. Organizations relying on agentscope for workflow automation or system management may face operational outages and data breaches. The critical severity and network exploitability make this a high-priority threat for cybersecurity teams worldwide.

Summary

CVE-2024-48050 is a critical vulnerability identified in the agentscope software, specifically in versions up to 0.0.4. The flaw exists in the is_callable_expression function located in the file agentscope\web\workstation\workflow_utils.py, where the Python eval() function is used to evaluate a string input 's'. Because eval() executes the passed string as Python code, if this input is user-controlled and not properly sanitized, it can lead to arbitrary code execution. This means an attacker can remotely execute any Python code on the affected system without authentication or user interaction, leading to full system compromise. The vulnerability is classified under CWE-94, which pertains to improper control of code generation or execution. The CVSS v3.1 score of 9.8 (critical) reflects the vulnerability's high exploitability (network vector, no privileges required, no user interaction) and severe impact on confidentiality, integrity, and availability. Although no public exploits have been reported yet, the presence of eval() on user input is a well-known risky practice, making this vulnerability highly exploitable in practice. The lack of available patches at the time of publication increases the urgency for organizations to implement mitigations or upgrade once fixes are released.

CWE-94Improper Control of Generation of Code ('Code Injection') (opens in a new tab)
Base weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #10OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
Architecture and Design · Refactoring
Refactor your program so that you do not have to dynamically generate code.
Architecture and Design
Run your code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which code can be executed by your product.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V5.2.8 (opens in a new tab)
V5.2.5 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
Leverage Executable Code in Non-Executable Files (opens in a new tab)
Manipulating User-Controlled Variables (opens in a new tab)
Code Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Feb 2026, 07:35 UTC

WeaknessesCWE-94

Technical details

References

Community reviews

Related threats