{"id":"CVE-2026-7679","title":"YunaiV yudao-cloud OAuth2TokenServiceImpl.java getAccessToken improper authentication","summary":"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. P…","severity":"high","cvss":7.3,"cvssVector":"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","cvssSource":"cna","cwe":["CWE-287"],"vendor":"YunaiV","product":"yudao-cloud","affected":["yudao-cloud 2026.01"],"ssvc":{"exploitation":"poc","automatable":"no","technicalImpact":"partial","timestamp":"2026-05-04T14:55:13.779067Z"},"exploitAvailable":true,"published":"2026-05-03","updated":"2026-10-27","sourceUpdated":"2026-10-27T07:22:32.665Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-7679","references":[{"url":"https://vuldb.com/vuln/360832","label":"VDB-360832 | YunaiV yudao-cloud OAuth2TokenServiceImpl.java getAccessToken improper authentication"},{"url":"https://vuldb.com/vuln/360832/cti","label":"VDB-360832 | CTI Indicators (IOB, IOC, IOA)"},{"url":"https://vuldb.com/cve/CVE-2026-7679","label":"CVE-2026-7679 | CVE Analysis and Report"},{"url":"https://vuldb.com/submit/800866","label":"Submit #800866 | YunaiV yudao-cloud up to 2026.01 Authentication Bypass by Primary Weakness"},{"url":"https://github.com/9str0IL/CVE/issues/1"}],"tags":["cve.org","exploit-available"],"epss":0.00416,"epssPercentile":0.35714,"ingestedAt":"2026-10-27T16:11:59.242Z","slug":"CVE-2026-7679","body":"## Overview\n\nA 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.\"\n\n## Affected\n\n- `yudao-cloud 2026.01`\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"midnight","depthScore":52,"depthScoreParts":{"impact":40.2,"likelihood":0.1,"exploitation":12,"ransomware":0},"changes":[]}