Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDiscover exposed Gradio interface
-
DeliverySubmit crafted document path targeting metadata service
-
ExploitServer issues unauthenticated HTTP request to 169.254.169.254
-
ExecutionRetrieve cloud IAM role credentials from parsed output
-
PersistAuthenticate to cloud provider API
-
ImpactEnumerate or exfiltrate cloud resources
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Credential Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that the Gradio interface be network-reachable by the attacker - either directly internet-exposed or accessible from an attacker-controlled internal segment. No authentication is required on the Gradio interface, and no non-default configuration or privileged setup is needed beyond a standard Qwen-Agent deployment. For the SSRF to yield sensitive data, the server must have network access to internal resources such as cloud metadata services or internal APIs; in isolated environments without such internal reachability, exploitability is significantly reduced. Exploitation is limited to confidentiality impact - no write or code-execution primitive is provided by this flaw in isolation. Deployments where the Gradio interface is firewalled exclusively to trusted hosts are not directly exploitable remotely. |
| Impact | The CVSS 4.0 score of 8.7 (AV:N/AC:L/AT:N/PR:N/UI:N/VC:H) accurately reflects the threat model: no authentication, no special preconditions, and a network-accessible trigger via Gradio's default unauthenticated configuration. The primary real-world risk is credential theft through cloud metadata service access - retrieving an AWS IMDSv1 token yields temporary IAM credentials that can pivot to broader cloud resource enumeration and exfiltration. This SSRF-to-metadata attack pattern is well-understood and frequently exploited in cloud penetration testing engagements, raising confidence that the attack path is practically viable. While no public exploit code has been confirmed and the CVE does not appear in the CISA KEV catalog at time of analysis, the zero-barrier exploitation path warrants urgent remediation for internet-exposed deployments. EPSS data is absent from the provided intelligence, so probabilistic exploitation likelihood cannot be quantified numerically. Risk is substantially reduced for deployments where the Gradio interface is restricted to private network segments, as network reachability is the sole prerequisite for exploitation. |
| Exploit ScenarioDerived | An attacker identifies an internet-accessible Qwen-Agent Gradio interface and submits a document parsing request with the path set to http://169.254.169.254/latest/meta-data/iam/security-credentials/, receiving the instance's IAM role name in the parsed output. A second request to the role-specific credential endpoint retrieves a temporary AWS AccessKeyId, SecretAccessKey, and SessionToken, which the attacker uses to authenticate to the AWS API and begin enumerating or exfiltrating cloud resources. No exploit code is publicly confirmed, but the attack requires only standard HTTP requests and knowledge of cloud metadata endpoint paths. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 28, 2026
Server-side request forgery in Qwen-Agent through 0.0.34 allows unauthenticated remote attackers to exfiltrate data from internal infrastructure by exploiting the document parsing path's failure to validate caller-supplied URLs. The Gradio interface - exposed without authentication by default - serves as the entry point, enabling attackers to direct the server to issue HTTP requests to cloud metadata endpoints such as AWS IMDSv1 or GCP metadata APIs and retrieve responses through the document parsing output. No public exploit code or CISA KEV listing exists at time of analysis, but the zero-privilege, zero-interaction attack vector against credential-bearing metadata services makes this a high-priority risk for any cloud-hosted deployment.
RemediationAI
No vendor-released patched version has been identified at time of analysis - available references point to a GitHub issue rather than a tagged release or vendor advisory confirming a fix; monitor https://github.com/QwenLM/Qwen-Agent for new releases. As an immediate compensating control, restrict access to the Gradio interface to trusted internal networks or authenticated reverse-proxy configurations, which eliminates the unauthenticated remote attack vector entirely. For cloud-hosted deployments, enforce IMDSv2-only access at the cloud platform level (AWS: set HttpTokens=required on instance metadata options; GCP: disable legacy metadata endpoints), which prevents SSRF-based metadata credential theft even if the SSRF flaw remains reachable - note this requires cloud-console configuration changes and carries no application-side side effects. Apply egress network controls restricting the Qwen-Agent process from connecting to RFC 1918 address ranges and link-local space (169.254.0.0/16) to reduce the effective SSRF target set. Continue monitoring the VulnCheck advisory at https://www.vulncheck.com/advisories/qwen-agent-server-side-request-forgery-via-caller-supplied-document-url for patch confirmation.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Qwen-Agent is an open-source LLM agent framework built on Alibaba's Qwen model family, affected through version 0.0.34 per CPE cpe:2.3:a:qwenlm:qwen-agent:*:*:*:*:*:*:*:*. The vulnerability resides specifically in qwen_agent/tools/simple_doc_parser.py, which handles document ingestion for agent workflows. The root cause is CWE-918 (Server-Side Request Forgery): the parser accepts caller-controlled path values and forwards them as outbound HTTP requests without enforcing URL scheme allowlisting or host/IP range validation. The Gradio web interface - the standard UI layer for exposing Qwen-Agent capabilities - is served without authentication by default, creating a publicly reachable trigger point for the SSRF. Cloud instance metadata services (AWS IMDSv1 at 169.254.169.254, GCP metadata at metadata.google.internal) are high-value targets because they expose instance credentials without requiring authentication from the requesting host, making them a natural SSRF pivot toward cloud resource compromise.
Know when Qwen Agent gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Unauthenticated network SSRF pivots to internal metadata services beyond the vulnerable component, changing scope; no integrity or availability impact applies.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
Qwen-Agent through 0.0.34 contains a server-side request forgery vulnerability in the document parsing path that treats caller-supplied paths as URLs without scheme restriction or host validation. Attackers can reach the unauthenticated Gradio interface to make the server issue HTTP requests to arbitrary internal addresses including metadata services and read retrieved content through parsed document output.
Executive ViewAI
Qwen-Agent versions through 0.0.34 expose a server-side request forgery vulnerability in the default Gradio interface that allows attackers without credentials to extract cloud authentication tokens from AWS and GCP metadata services. Organizations operating Qwen-Agent in cloud environments face immediate risk of compromised cloud credentials and unauthorized access to their infrastructure and data.
No vendor-released patch identified at time of analysis. Implement network segmentation and egress filtering to deny traffic to metadata service endpoints; disable or restrict the Gradio interface via firewall, reverse proxy, or WAF to limit access to trusted internal networks only; apply IAM roles with minimal required permissions to reduce blast radius if credentials are compromised; enable detailed logging of all outbound requests from Qwen-Agent instances to detect exploitation attempts; consider immediate suspension of Qwen-Agent deployments in production until patched version becomes available.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.
EUVD-2026-67799
GHSA-h9q8-qvr9-h4c6
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB