# CVE-2026-51152: Server-side request forgery in n/a

> Unauthenticated attackers can exploit SSRF in the /har/test endpoint to access internal network resources and cloud metadata via unvalidated user-supplied URLs.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2026
- **Updated:** 1 Sep 2026
- **Also known as:** GHSA-cgg6-cpqj-xc4m

## What is CVE-2026-51152?

CVE-2026-51152 is a critical server-side request forgery vulnerability in n/a, published on 31 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Server-side request forgery (SSRF) in the /har/test endpoint in QD 20220208 through 20250803. Fetcher.build_request() in libs/fetcher.py constructs an httpclient.HTTPRequest from user-supplied JSON without validating URL scheme, host, or IP range. The /har/test handler does not require authentication, enabling unauthenticated remote attackers to force the QD server to send arbitrary HTTP requests to internal network resources and cloud metadata endpoints. validate_cert is set to False, disabling TLS verification.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-51152?


## How do I fix CVE-2026-51152?

No fix has been published for CVE-2026-51152 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-51152 being exploited?

There is no known exploitation of CVE-2026-51152 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-51152 and fix it if it is affected.

What it is: CVE-2026-51152 is a critical server-side request forgery vulnerability in n/a, published on 31 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-51152 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-51152/ (Markdown: https://insights.sbomify.com/CVE-2026-51152/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-51152
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-51152
- OSV: https://osv.dev/vulnerability/CVE-2026-51152

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-51152/
Summaries are generated and may contain mistakes; the official description above is the record.