Quick answers
- Is CVE-2026-122016 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-122016 being exploited in the wild.
- How severe is CVE-2026-122016?
- Medium severity, with a CVSS score of 6.3, published 4 November 2026.
- Which products and versions are affected?
- Yangzongzhuan RuoYi-Vue up to 3.9.2.
- Is there a fix for CVE-2026-122016?
- No fixed version is recorded yet. Restrict menu management and role editing privileges to trusted administrators only. Validate that the perms field in menu creation and update operations rejects the reserved wildcard *:*:* before persisting to the database. 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-122016 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-122016?
- Check whether you run Yangzongzhuan RuoYi-Vue 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.
How to fix
Restrict menu management and role editing privileges to trusted administrators only. Validate that the perms field in menu creation and update operations rejects the reserved wildcard *:*:* before persisting to the database.
Technical details
The vulnerability is an improper privilege management flaw (CWE-863/CWE-269) in the SysPermissionService.getMenuPermission function. The permission framework reserves the wildcard *:*:* as a marker for full admin access, but the menu permissions table accepts any input without validation. An authenticated user with menu and role management rights can create a menu with perms='*:*:*', assign it to their role, and gain full system permissions that pass all authorization checks. The attack requires prior authorization to system:menu:add/edit and system:role:edit with appropriate data scope.
Affected products
- yangzongzhuan RuoYi-Vue up to 3.9.2
Timeline
- 2026-10-11: disclosed: Vulnerability reported on GitHub issue #206
- 2026-11-04: advisory