Quick answers
- Is CVE-2026-58448 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58448 being exploited in the wild.
- How severe is CVE-2026-58448?
- Medium severity, with a CVSS score of 6.5, published 30 June 2026.
- Which products and versions are affected?
- YunaiV Yudao-Cloud < 2026.06.
- Is there a fix for CVE-2026-58448?
- A patch was published on 2026-06-30: Fixed in version 2026.06 release Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-58448 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-58448?
- Check whether you run YunaiV Yudao-Cloud at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A broken access control vulnerability exists in the BPM module of yudao-cloud due to a missing authorization check. Specifically, the 'get-bpmn-model-view' endpoint in BpmProcessInstanceController.java lacks the @PreAuthorize annotation used by other endpoints in the same controller. An authenticated attacker can exploit this by sending a GET request to '/bpm/process-instance/get-bpmn-model-view' with a specific process-instance ID. This allows the retrieval of sensitive data including form variables, approver identities, rejection comments, and BPMN XML definitions without ownership or tenant verification. The vulnerability is addressed in version 2026.06.
Affected products
- YunaiV yudao-cloud < 2026.06
Timeline
- 2026-06-30: disclosed: Vulnerability reported via GitHub Issue #315
- 2026-06-30: patched: Fixed in version 2026.06 release
- 2026-06-30: advisory