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

Back
New CVE Detected

CVE-2026-82285 – Unauthenticated SSRF – Bisheng ≤ 2.6.0-fix2

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-82285 is an unauthenticated Server-Side Request Forgery (SSRF) vulnerability in Bisheng, affecting all versions through 2.6.0-fix2. The flaw resides in the POST /api/v1/workflow/report/callback endpoint, which accepts a caller-supplied URL with no authentication, scheme restriction, or host filtering. The vulnerability is rated HIGH severity and is remotely exploitable without any credentials or user interaction.

Technical details

  • Root cause: the /api/v1/workflow/report/callback endpoint in workflow.py forwards a caller-controlled URL/host without validating scheme or destination.
  • Trigger conditions: an attacker sends a crafted POST request to the callback endpoint specifying an arbitrary target URL; no authentication is required.
  • Attack vector: Network — the endpoint is reachable directly over HTTP(S) from an unauthenticated remote position.
  • Impact: attackers can probe internal network services and cloud instance metadata endpoints, and retrieve captured responses via caller-supplied object names from associated object storage, leading to internal reconnaissance and potential disclosure of sensitive data/credentials.

Affected software

  • dataelement Bisheng: all versions from the start of the project through 2.6.0-fix2

Severity

  • CVSS v3.1: 8.2 (HIGH) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
  • CVSS v4.0: 8.8 (HIGH) — 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

Mitigation and recommended actions

  • Immediate: upgrade Bisheng to a fixed release beyond 2.6.0-fix2 once available from the vendor; monitor the vendor repository/advisory for the patched version.
  • If no patch is deployed yet: restrict or disable public exposure of the /api/v1/workflow/report/callback endpoint, enforce authentication and host/scheme allow-listing at a reverse proxy or WAF in front of the application, and block outbound requests from the application host to cloud metadata IP ranges (e.g., 169.254.169.254) and internal RFC1918 ranges.

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