Vulnerability · Published May 3, 2026 · Assigned by VulDB
CVE-2026-7679YunaiV yudao-cloud OAuth2TokenServiceImpl.java getAccessToken improper authentication
High 7.3
In plain English
A high-severity improper authentication in yudao-cloud from YunaiV. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.4% (higher than 36% of all known vulnerabilities).
Official description
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."
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| YunaiV | yudao-cloud | 2026.01 |
Weakness: CWE-287 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:C
References
- VDB-360832 | YunaiV yudao-cloud OAuth2TokenServiceImpl.java getAccessToken improper authentication vdb-entry, technical-description
- VDB-360832 | CTI Indicators (IOB, IOC, IOA) signature, permissions-required
- CVE-2026-7679 | CVE Analysis and Report third-party-advisory
- Submit #800866 | YunaiV yudao-cloud up to 2026.01 Authentication Bypass by Primary Weakness third-party-advisory
- https://github.com/9str0IL/CVE/issues/1 exploit, issue-tracking