YunaiV yudao-cloud OAuth2TokenServiceImpl.java getAccessToken improper authentication
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."
- Products
- yudao-cloud
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-7679
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 31 Oct 2026, 13:38 UTC · Revision 1
Source evidence
YunaiV yudao-cloud OAuth2TokenServiceImpl.java getAccessToken improper authentication
core-cve · Original sourcePublished 3 May 2026, 04:15 UTC
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."
cve:CVE-2026-7679
yudao-cloud
Fixed versions: Not specified
Complete source record
{
"id": "aed0714849955e7c4897b0ec0d8e099b931e024dc681af1cd0a11ac029027a20",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-7679",
"method": "structured",
"payload": {
"kind": "advisory",
"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. 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.\"",
"evidence": "cve:CVE-2026-7679",
"products": [
{
"name": {
"value": "yudao-cloud",
"evidence": "/containers/cna/affected/0/product"
},
"prerequisites": [],
"fixed_versions": [],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2026-7679",
"aliases": [
"CVE-2026-7679"
],
"metrics": [
{
"cvssV4_0": {
"version": "4.0",
"baseScore": 6.9,
"baseSeverity": "MEDIUM",
"vectorString": "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"
}
},
{
"cvssV3_1": {
"version": "3.1",
"baseScore": 7.3,
"baseSeverity": "HIGH",
"vectorString": "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"
}
},
{
"cvssV3_0": {
"version": "3.0",
"baseScore": 7.3,
"baseSeverity": "HIGH",
"vectorString": "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"
}
},
{
"cvssV2_0": {
"version": "2.0",
"baseScore": 7.5,
"vectorString": "AV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:ND/RC:C"
}
}
],
"affected": [
{
"cpes": [
"cpe:2.3:a:yunaiv:yudao-cloud:*:*:*:*:*:*:*:*"
],
"vendor": "YunaiV",
"product": "yudao-cloud",
"versions": [
{
"status": "affected",
"version": "2026.01"
}
]
}
],
"modified": "2026-10-27T07:22:32.665Z",
"provider": "cve",
"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"
],
"provider_metadata": {
"adp": [
{
"title": "CISA ADP Vulnrichment",
"metrics": [
{
"other": {
"type": "ssvc",
"content": {
"id": "CVE-2026-7679",
"role": "CISA Coordinator",
"options": [
{
"Exploitation": "poc"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"version": "2.0.3",
"timestamp": "2026-05-04T14:55:13.779067Z"
}
}
}
],
"providerMetadata": {
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP",
"dateUpdated": "2026-05-04T14:55:27.068Z"
}
}
],
"cna": {
"orgId": "1af790b2-7ee1-4545-860a-a788eba489b5",
"shortName": "VulDB",
"dateUpdated": "2026-10-27T07:22:32.665Z"
}
}
},
"related_cves": [
{
"value": "CVE-2026-7679",
"evidence": "/cveMetadata/cveId"
}
],
"security_relevant": true,
"severity_evidence": "/containers/cna/metrics"
},
"source_id": "core-cve",
"document_id": 391524,
"published_at": "2026-05-03T04:15:10.929+00:00"
}