{"id":"CVE-2026-7679","revision":"b07200927c55495690067ab7f5bde504","records":[{"revision":"b07200927c55495690067ab7f5bde504","observedAt":"2026-10-27T09:00:34.147+00:00","statement":{"source":"cve-program","id":"CVE-2026-7679","aliases":[],"title":"YunaiV yudao-cloud OAuth2TokenServiceImpl.java getAccessToken improper authentication","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.\"","state":0,"publishedAt":"2026-05-03T04:15:10.929+00:00","modifiedAt":"2026-10-27T07:22:32.665+00:00","affected":[{"ecosystem":"Vendor product","name":"yudao-cloud","ranges":[],"versions":[],"rawVersionEvidence":"{\n                    \"vendor\": \"YunaiV\",\n                    \"product\": \"yudao-cloud\",\n                    \"versions\": [\n                        {\n                            \"version\": \"2026.01\",\n                            \"status\": \"affected\"\n                        }\n                    ],\n                    \"cpes\": [\n                        \"cpe:2.3:a:yunaiv:yudao-cloud:*:*:*:*:*:*:*:*\"\n                    ]\n                }"}],"metrics":[{"system":"CVSS 4.0","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P","score":6.9,"severity":"MEDIUM"},{"system":"CVSS 3.1","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","score":7.3,"severity":"HIGH"},{"system":"CVSS 3.0","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:C","score":7.3,"severity":"HIGH"},{"system":"CVSS 2.0","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:ND/RC:C","score":7.5,"severity":null}],"references":["https://vuldb.com/vuln/360832","https://vuldb.com/vuln/360832/cti","https://vuldb.com/cve/CVE-2026-7679","https://vuldb.com/submit/800866","https://github.com/9str0IL/CVE/issues/1"],"sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-7679","license":"CVE Program Terms of Use","key":"cve-program:CVE-2026-7679","identifiers":["CVE-2026-7679"]},"retained":false,"historicalAffected":[]}],"coverage":[]}