# CVE-2026-92566: DataGear through 6.0.0 Unauthenticated SSRF via HTTP Dataset Preview

> Unauthenticated attackers can exploit an SSRF vulnerability in DataGear to access internal services and cloud metadata via the HTTP dataset preview endpoint.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-fjfv-cm2f-px7c

## What is CVE-2026-92566?

CVE-2026-92566 is a high-severity server-side request forgery vulnerability in datageartech datagear, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

DataGear through 6.0.0 contains a server-side request forgery vulnerability in the /dataSet/preview/Http endpoint that allows unauthenticated attackers to execute arbitrary HTTP requests by supplying a caller-controlled URI. Attackers can issue GET, POST, PUT, PATCH, or DELETE requests to internal endpoints and cloud metadata services, receiving full response bodies without authentication or validation.

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

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


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

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

## Is CVE-2026-92566 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92566 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92566 is a high-severity server-side request forgery vulnerability in datageartech datagear, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92566 exists.

Affected product: datageartech datagear. 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-92566/ (Markdown: https://insights.sbomify.com/CVE-2026-92566/index.md)
```

## Sources

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

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