Quick answers
- Is CVE-2026-102616 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-102616 being exploited in the wild.
- How severe is CVE-2026-102616?
- High severity, with a CVSS score of 7.3, published 29 September 2026.
- Which products and versions are affected?
- Risesoft y9 WorkFlow-Engine up to 9.6.10.
- Is there a fix for CVE-2026-102616?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-102616 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-102616?
- Check whether you run Risesoft y9 WorkFlow-Engine 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
The OAuth2 Resource Filter protecting the processadmin front end does not cover the /services/rest/* path, which is guarded only by CommonParamsFilter that validates tenant headers but no token. The HistoricProcessApiImpl.getByIdAndYear method in CustomHistoricProcessServiceImpl.java concatenates user-supplied year and processInstanceId parameters directly into a SQL query without parameterization, enabling boolean blind SQL injection at two injection points. Remote unauthenticated exploitation is possible and proof-of-concept code is publicly available.
Affected products
- Risesoft y9 WorkFlow-Engine up to 9.6.10
Timeline
- 2026-09-29: disclosed