Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-82268 – Server-Side Request Forgery (SSRF) – Qwen-Agent ≤ 0.0.34

Be the first to know when new zero-days emerge:

Summary

CVE-2026-82268 is a Server-Side Request Forgery (SSRF) vulnerability in Qwen-Agent, an open-source agent framework built on the Qwen LLM family. The flaw resides in the document parsing path, which treats caller-supplied paths as URLs without any scheme restriction or host validation, allowing unauthenticated remote attackers to force the server to issue HTTP requests to arbitrary internal or external addresses. The issue affects Qwen-Agent through version 0.0.34 and has been assigned a CVSS v4.0 base score of 8.7 (High).

Technical details

  • Root cause: The document parsing logic (qwen_agent/tools/simple_doc_parser.py) accepts caller-supplied file paths and processes them as URLs without validating the scheme (e.g., blocking file://, gopher://, etc.) or verifying that the target host is not an internal/restricted address.
  • Trigger conditions: An attacker submits a crafted document path/URL to the document parsing tool via the exposed, unauthenticated Gradio interface that many Qwen-Agent deployments run by default.
  • Attack vector: Network-based, no authentication or user interaction required (AV:N/AC:L/PR:N/UI:N per the CVSS v3.1 vector).
  • Impact: The server can be coerced into making requests to arbitrary internal addresses, including cloud metadata services (e.g., AWS/GCP/Azure instance metadata endpoints), potentially exposing sensitive internal data, credentials, or network topology. Retrieved content is returned to the attacker through the parsed document output, resulting in high confidentiality impact with no direct integrity or availability impact.

Affected software

  • Product: Qwen-Agent (qwen-agent PyPI package)
  • Vendor: QwenLM
  • Affected versions: All versions through 0.0.34

Severity

  • CVSS v3.1: 7.5 (High) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
  • CVSS v4.0: 8.7 (High) — 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

Mitigation and recommended actions

  • Immediate: No fixed release version has been published by the vendor at this time. Organizations should monitor the QwenLM/Qwen-Agent GitHub repository and issue tracker for an official patch and upgrade as soon as one becomes available.
  • Workarounds / network mitigations (until a patch is released):
    • Do not expose the Qwen-Agent Gradio interface directly to the internet; place it behind authentication and restrict access via VPN, allow-listing, or a reverse proxy requiring credentials.
    • Block or restrict outbound requests from the Qwen-Agent host to cloud metadata service addresses (e.g., 169.254.169.254) and other internal/private IP ranges using egress firewall rules or an internal proxy with strict allow-listing.
    • Disable or remove the document parsing feature if it is not required for your deployment.
    • Apply network segmentation so the Qwen-Agent host cannot reach sensitive internal services.
    • Monitor logs for anomalous outbound HTTP requests originating from the document parsing tool, particularly requests to internal IP ranges or metadata endpoints.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge