Medium · CVSS 6.9CVE-2026-7679

YunaiV yudao-cloud OAuth2TokenServiceImpl.java getAccessToken improper authenticationCVE-2026-7679

Answer in brief

CVE-2026-7679 records a Medium severity (CVSS 6.9) vulnerability in YunaiV yudao-cloud OAuth2TokenServiceImpl.java getAccessToken improper authentication. The current sources do not mark it as known exploited. The current feed maps YunaiV/yudao-cloud (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published May 3, 2026Updated Oct 27, 2026Source checked Oct 27, 2026First seen by HOL Oct 27, 2026Material review Oct 27, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 6.9
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

CVSS is 6.9. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps YunaiV/yudao-cloud (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
YunaiV/yudao-cloudgeneric	2026.01	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for YunaiV/yudao-cloud.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
May 3, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 27, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Oct 27, 2026

Sources and claim methodology

Upstream source 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."

Quoted source text, attributed separately from HOL analysis.