# CVE-2026-82285: BISHENG Unauthenticated Server-Side Request Forgery via Workflow Report Callback

> Unauthenticated attackers can exploit an SSRF vulnerability in BISHENG to access internal network services and cloud metadata endpoints.

- **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:** 28 Aug 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-qch5-28r4-f5gj

## What is CVE-2026-82285?

CVE-2026-82285 is a high-severity server-side request forgery vulnerability in dataelement bisheng, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

bisheng through 2.6.0-fix2 contains a server-side request forgery vulnerability in the POST /api/v1/workflow/report/callback endpoint that lacks authentication and applies no URL scheme restrictions or host filtering. Unauthenticated attackers can supply arbitrary URLs to enumerate internal network services and cloud metadata endpoints, then retrieve captured responses from object storage using caller-supplied object names.

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

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


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

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

## Is CVE-2026-82285 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82285 is a high-severity server-side request forgery vulnerability in dataelement bisheng, published on 28 Aug 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-82285 exists.

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

## Sources

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

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