{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7679 exists.","fix":"No fix has been published for CVE-2026-7679 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-7679 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7679 exists.\n\nAffected product: YunaiV yudao-cloud. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-7679/ (Markdown: https://insights.sbomify.com/CVE-2026-7679/index.md)","id":"CVE-2026-7679","markdown":"https://insights.sbomify.com/CVE-2026-7679/index.md","name":"CVE-2026-7679","record":{"aliases":["GHSA-vgp3-r337-849c"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["privilege_escalation","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Java microservices framework","requires_auth":"none","summary":"Remote attackers can bypass authentication in the getAccessToken function to gain unauthorized access to the yudao-cloud system.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-287","name":"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.\"","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"YunaiV yudao-cloud OAuth2TokenServiceImpl.java getAccessToken improper authentication","id":"CVE-2026-7679","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"jsbroks COCO Annotator Data Endpoint datasets.py path traversal","id":"CVE-2026-7680"},"packages":[],"prev":{"headline":"YunaiV yudao-cloud GoViewDataServiceImpl.java getDataBySQL sql injection","id":"CVE-2026-7678"},"products":["yudao-cloud"],"published":"2026-05-03","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-27","vendors":["YunaiV"]},"summary":"Remote attackers can bypass authentication in the getAccessToken function to gain unauthorized access to the yudao-cloud system.","url":"https://insights.sbomify.com/CVE-2026-7679/"}