# CVE-2026-7679: YunaiV yudao-cloud OAuth2TokenServiceImpl.java getAccessToken improper authentication

> Remote attackers can bypass authentication in the getAccessToken function to gain unauthorized access to the yudao-cloud system.

- **Severity:** Medium 6.9 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 May 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-vgp3-r337-849c

## What is CVE-2026-7679?

CVE-2026-7679 is a medium-severity authentication bypass vulnerability in YunaiV yudao-cloud, published on 3 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### 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."

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-7679?


## How do I fix CVE-2026-7679?

No fix has been published for CVE-2026-7679 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-7679 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7679 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-7679 and fix it if it is affected.

What it is: CVE-2026-7679 is a medium-severity authentication bypass vulnerability in YunaiV yudao-cloud, published on 3 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7679 exists.

Affected product: YunaiV yudao-cloud. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-7679/ (Markdown: https://insights.sbomify.com/CVE-2026-7679/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-7679
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-7679
- OSV: https://osv.dev/vulnerability/CVE-2026-7679

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-7679/
Summaries are generated and may contain mistakes; the official description above is the record.