# CVE-2026-58448: yudao-cloud < 2026.06 - BPM Module Broken Access Control via process-instance API

> Authenticated users can read arbitrary workflow data by accessing an unprotected API endpoint without proper authorization checks.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jun 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-f6rh-2m88-w48m

## What is CVE-2026-58448?

CVE-2026-58448 is a high-severity missing authorization vulnerability in YunaiV yudao-cloud, published on 30 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

yudao-cloud before 2026.06 contains a broken access control vulnerability in the BPM module that allows any authenticated user to access arbitrary process instance records by supplying a caller-controlled process-instance identifier to an unprotected endpoint lacking the @PreAuthorize annotation. Attackers can query any process-instance identifier through the unguarded GET endpoint to read sensitive workflow data including submitted form variables, approver identities, approval and rejection comments, and process BPMN XML without ownership or tenant party verification.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-58448 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-58448 is a high-severity missing authorization vulnerability in YunaiV yudao-cloud, published on 30 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-58448 exists.

Affected product: YunaiV yudao-cloud. 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-58448/ (Markdown: https://insights.sbomify.com/CVE-2026-58448/index.md)
```

## Sources

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

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