Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-110215 Overview
CVE-2026-110215 is a missing authorization vulnerability [CWE-862] affecting the youlai-boot Spring Boot framework through version 2.21.1. The flaw resides in the role-menu assignment endpoint PUT /api/v1/roles/{roleId}/menus, which fails to validate whether the calling user has sufficient privileges to modify the targeted role's permissions. Authenticated low-privileged users, including the built-in GUEST test account, can assign arbitrary menu and button permissions to their own role. After the Redis permission cache refreshes, the attacker obtains administrator-equivalent access to the application.
Critical Impact
Any authenticated user, including the default GUEST account, can escalate to administrator by self-assigning all menu and button permissions through the role-menu endpoint.
Affected Products
- youlai-boot framework versions through 2.21.1
- Applications deploying youlai-boot with default role configurations
- Instances exposing the GUEST or similar low-privileged test accounts
Discovery Timeline
- 2026-10-13 - CVE-2026-110215 published to NVD
- 2026-10-13 - Last updated in NVD database
Technical Details for CVE-2026-110215
Vulnerability Analysis
The vulnerability stems from an authorization gap in the RoleController.updateRoleMenus method of youlai-boot. The endpoint PUT /api/v1/roles/{roleId}/menus accepts a role identifier and a list of menu permission IDs. The controller enforces authentication but does not verify that the requester has administrative rights to modify the specified role. A user can therefore target their own role identifier and submit the full menu permission tree.
The downstream RoleServiceImpl persists the submitted permissions and refreshes the Redis permission cache. On the next request, the attacker's session reflects the new administrative permissions without requiring re-authentication. This converts a routine authorization oversight into a full privilege escalation path.
Root Cause
The root cause is a missing authorization check [CWE-862] on a privileged state-changing endpoint. The method relies solely on authentication filters and the presence of a generic permission marker, rather than validating role scope or ownership. There is no verification that the caller holds a role capable of granting the requested permissions.
Attack Vector
An attacker authenticates with a low-privileged account such as GUEST. The attacker issues a PUT request to /api/v1/roles/{roleId}/menus targeting the identifier of their own role, with a request body containing all menu and button permission IDs. The server writes the new permissions and refreshes the Redis cache, granting the attacker administrator-equivalent access on subsequent requests.
// Patch excerpt from commit 36d2db6 - permission identifier hardening
@Operation(summary = "系统配置分页列表")
@GetMapping("/page")
- @PreAuthorize("@ss.hasPerm('sys:config:query')")
+ @PreAuthorize("@ss.hasPerm('sys:config:list')")
@Log( value = "系统配置分页列表",module = LogModuleEnum.SETTING)
public PageResult<ConfigVO> page(@ParameterObject ConfigPageQuery configPageQuery) {
IPage<ConfigVO> result = configService.page(configPageQuery);
Source: GitHub Commit #36d2db6
Detection Methods for CVE-2026-110215
Indicators of Compromise
- Unexpected PUT /api/v1/roles/{roleId}/menus requests originating from non-administrative accounts such as GUEST.
- Sudden expansion of a low-privileged role's menu permission list in the sys_role_menu database table.
- Redis permission cache refresh events (sys:perms:* keys) correlated with non-admin session tokens.
- Audit log entries showing menu assignment actions performed by users outside the administrator role.
Detection Strategies
- Deploy web application firewall (WAF) rules that restrict PUT /api/v1/roles/*/menus to known administrator session identifiers.
- Instrument the RoleController to emit structured audit events including caller principal, target role, and permission delta.
- Correlate authentication logs with permission changes to flag self-elevation patterns where the caller's role is also the modified role.
Monitoring Recommendations
- Alert on any role-menu modification performed by accounts flagged as test, demo, or guest.
- Monitor Redis for permission cache invalidations that are not preceded by an administrator session.
- Baseline the frequency of role permission changes and alert on deviations outside normal change windows.
How to Mitigate CVE-2026-110215
Immediate Actions Required
- Disable or rotate credentials for the GUEST and any other default low-privileged accounts shipped with youlai-boot.
- Restrict network access to the /api/v1/roles/* endpoint family to administrative users at the reverse proxy layer.
- Audit the sys_role_menu table for unauthorized permission grants and revoke suspicious entries.
Patch Information
Review the upstream remediation in GitHub Commit #36d2db6, which revises permission identifiers across the controller layer. Additional technical analysis is available in the VulnCheck Advisory on Privilege Escalation and the HackMD Authorization Issue Analysis. Upgrade beyond version 2.21.1 once a fixed release is published by the maintainers.
Workarounds
- Add a server-side check in RoleController.updateRoleMenus that rejects requests where the target roleId matches the caller's own role.
- Enforce a @PreAuthorize("@ss.hasPerm('sys:role:update')") annotation that is only granted to the administrator role.
- Remove or lock the GUEST demo account in production deployments and revoke any permissions it currently holds.
# Example reverse proxy rule to restrict role-menu modifications
location ~ ^/api/v1/roles/[0-9]+/menus$ {
if ($request_method = PUT) {
set $block 1;
}
if ($http_x_user_role != "ADMIN") {
set $block "${block}1";
}
if ($block = "11") {
return 403;
}
proxy_pass http://youlai_backend;
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

