Is CVE-2026-51152 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-51152 being exploited in the wild.

How severe is CVE-2026-51152?

Critical severity, with a CVSS score of 9.1, published 31 August 2026.

Is there a fix for CVE-2026-51152?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-51152 attacked?

It is attacked over the network.

Am I affected by CVE-2026-51152?

Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-51152: QD server-side request forgery in /har/test endpoint

CVE-2026-51152 · Severity: critical · CVSS 9.1 · Published 2026-08-31

QD is a web framework for automating HTTP-based tasks. An unauthenticated attacker can exploit a vulnerability in the /har/test endpoint to force the QD server to make arbitrary HTTP requests to internal network resources, cloud metadata services, or other internal systems. This enables attackers to access sensitive credentials, reconnaissance of internal infrastructure, or attack internal services—all without requiring authentication or valid user credentials.

Quick answers

Is CVE-2026-51152 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-51152 being exploited in the wild.
How severe is CVE-2026-51152?: Critical severity, with a CVSS score of 9.1, published 31 August 2026.
Which products and versions are affected?: QD 20220208 through 20250803.
Is there a fix for CVE-2026-51152?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-51152 attacked?: It is attacked over the network.
Am I affected by CVE-2026-51152?: Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is a server-side request forgery (SSRF) in the Fetcher.build_request() method within libs/fetcher.py. The /har/test HTTP endpoint constructs an httpclient.HTTPRequest from user-supplied JSON without validating the URL scheme, host, or IP address range. The vulnerable handler lacks the @authenticated decorator, allowing unauthenticated remote attackers to send requests to internal RFC1918 ranges (127.0.0.0/8, 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, 169.254.0.0/16) and cloud metadata endpoints (e.g., AWS IMDSv1 at 169.254.169.254). TLS certificate verification is disabled (validate_cert=False), further facilitating attacks. Network access to the QD server on the vulnerable port is the only precondition.

Affected products

QD 20220208 through 20250803

Timeline

2026-08-31: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.