Auth bypass in Yunaiv Yudao-Cloud
CVE-2026-7679
A security flaw has been discovered in YunaiV yudao-cloud up to 2026.01. This impacts the function getAccessToken of the file yudao-module-system-biz/src/main/java/io/github/ruoyi/common/oauth2/service/impl/OAuth2TokenServiceImpl.java. Performing a manipulation results in improper authentication. The attack can be initiated remotely. The exploit has been released to the public and may be used for attacks. The vendor explains: "[W]e intentionally retain the existing generic compatibility path that accepts a valid, unexpired stored refresh token when an access-token lookup is unavailable, for integrations such as reports and WebSocket. We are not introducing strict access-token-only verification, new revocation behavior or a separate trusted-entry API. This is a retained compatibility decision, not a claim that this behavior follows the standard OAuth separation or that every identity/revocation scenario has been eliminated."
Vulnerability class: Broken Authentication
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.3 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L.
EPSS exploit prediction
EPSS 0.004, 36.4th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Yunaiv Yudao-Cloud — versions 2026.01
Weakness classification (CWE)
References
- VDB-360832 | YunaiV yudao-cloud OAuth2TokenServiceImpl.java getAccessToken improper authentication (technical-description, vdb-entry)
- VDB-360832 | CTI Indicators (IOB, IOC, IOA) (signature, permissions-required)
- Submit #800866 | YunaiV yudao-cloud up to 2026.01 Authentication Bypass by Primary Weakness (third-party-advisory)
- github.com/9str0IL/CVE/issues/1 (issue-tracking, exploit)
- CVE-2026-7679 | CVE Analysis and Report (third-party-advisory)