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

Back
New CVE Detected

CVE-2026-51152 – Unauthenticated SSRF – QD 20220208 through 20250803

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-51152 is a Server-Side Request Forgery (SSRF) vulnerability affecting QD (QD-Today), a Chinese-language HTTP request scheduling framework built on HAR Editor and Tornado Server. The unauthenticated /har/test endpoint allows attackers to force the QD server to issue arbitrary outbound HTTP requests to internal network resources and cloud metadata services. The flaw carries a CVSS v3.1 base score of 9.1 (Critical).

Technical details

  • Root cause: Fetcher.build_request() in libs/fetcher.py constructs outbound HTTP requests from user-supplied JSON without validating the URL scheme, host, or IP address range, and disables TLS certificate verification (validate_cert=False).
  • Trigger condition: the /har/test endpoint lacks an authentication decorator, so any unauthenticated client can submit a crafted JSON request body specifying an arbitrary target URL (e.g., http://127.0.0.1:6379/ or a cloud metadata address) for QD to fetch on its behalf.
  • Attack vector: network, requiring no privileges or user interaction — a single unauthenticated HTTP POST to /har/test.
  • Impact: high confidentiality and integrity impact via server-side proxying to internal-only services and cloud instance metadata endpoints, potentially exposing credentials or internal data; no direct availability impact.

Affected software

  • QD (QD-Today) versions 20220208 through 20250803

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate: no fixed release is currently identified in the public CVE record; monitor the QD-Today GitHub repository for a patched release beyond version 20250803 and upgrade as soon as one is available.
  • If no patch is available: restrict or disable public access to the /har/test endpoint, place QD instances behind authentication or a reverse proxy that enforces access control, and block outbound requests from the QD host to loopback addresses, RFC1918 private ranges, and cloud metadata IPs (e.g., 169.254.169.254) via egress network filtering.
  • Additionally, avoid exposing QD directly to the internet where not required, and review logs for anomalous requests to /har/test targeting internal or metadata addresses.

References

Are you exposed?

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge