CVE-2026-6606
Received Received - Intake
Server-Side Request Forgery in Modelscope Agentscope _process_audio_block

Publication date: 2026-04-20

Last updated on: 2026-04-29

Assigner: VulDB

Description
A weakness has been identified in modelscope agentscope up to 1.0.18. This vulnerability affects the function _process_audio_block of the file src/agentscope/agent/_agent_base.py. Executing a manipulation of the argument url can lead to server-side request forgery. It is possible to launch the attack 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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-20
Last Modified
2026-04-29
Generated
2026-05-07
AI Q&A
2026-04-20
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
modelscope agentscope to 1.0.18 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability exists in modelscope agentscope up to version 1.0.18, specifically in the function _process_audio_block within the file src/agentscope/agent/_agent_base.py.

An attacker can manipulate the argument 'url' passed to this function to perform a server-side request forgery (SSRF) attack.

This means the attacker can make the server send unauthorized requests to other internal or external resources, potentially bypassing security controls.

The attack can be launched remotely, and the exploit code has been publicly disclosed.


How can this vulnerability impact me? :

This vulnerability can allow an attacker to make the affected server send unauthorized requests to internal or external systems.

Potential impacts include unauthorized access to internal services, data leakage, or use of the server as a proxy for further attacks.

Because the exploit is publicly available and the attack can be performed remotely without authentication, the risk of exploitation is significant.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The provided information does not specify any direct impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by monitoring for unusual or unauthorized requests to the _process_audio_block function that involve URLs being fetched without validation, especially those using the file:// scheme or unusual network requests indicative of SSRF attempts.

Since the vulnerability involves the use of urllib.request.urlopen() fetching URLs from audio blocks, detection can focus on identifying requests or logs where URLs with file:// or unexpected protocols are processed.

  • Check application logs for errors related to wave.Error exceptions, which may indicate attempts to include local files.
  • Monitor network traffic for outbound requests from the AgentScope service to internal or unusual IP addresses or file:// URLs.
  • Use commands like `grep '_process_audio_block' /path/to/logs` or `grep 'wave.Error' /path/to/logs` to find relevant error logs.
  • Use network monitoring tools (e.g., tcpdump or Wireshark) to capture outgoing requests from the AgentScope process to detect SSRF attempts.

What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include restricting or disabling the vulnerable functionality that processes audio URLs without validation.

Specifically, implement input validation to block unsupported URL schemes such as file:// and limit URL fetching to trusted domains or protocols.

  • Apply network-level controls to prevent the AgentScope service from making arbitrary outbound requests, especially to internal or sensitive network resources.
  • Monitor and limit memory usage to detect and prevent denial of service attacks caused by unbounded response reads.
  • If possible, update or patch AgentScope to a version where this vulnerability is fixed (note: vendor has not responded, so patch availability may be limited).
  • Consider disabling or isolating the audio playback feature until a fix is available.

Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart