yudao-cloud CVE-2026-7710

Q: What is the CVSS score of CVE-2026-7710?

CVE-2026-7710 has a CVSS 4.0 base score of 5.5 (Medium). CVSS 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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.1%.

MEDIUM

Improper Authentication (CWE-287)

2026-05-04 cna@vuldb.com

Java Authentication Bypass

5.5

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

5.5 MEDIUM

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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Lifecycle Timeline

Analysis Generated

May 04, 2026 - 00:30 vuln.today

Analysis Generated

May 04, 2026 - 00:22 vuln.today

CVE Published

May 04, 2026 - 00:16 nvd

MEDIUM 5.5

DescriptionCVE.org

A security flaw has been discovered in YunaiV yudao-cloud up to 3.8.0. This affects the function doFilterInternal of the file JwtAuthenticationTokenFilter.java of the component Ruoyi-Vue-Pro. Performing a manipulation of the argument mock-token results in improper authentication. Remote exploitation of the attack is possible. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

AnalysisAI

Authentication bypass in YunaiV yudao-cloud up to version 3.8.0 allows remote unauthenticated attackers to manipulate the mock-token argument in JwtAuthenticationTokenFilter.java, circumventing JWT authentication mechanisms and gaining unauthorized access. The vulnerability affects the Ruoyi-Vue-Pro component, has publicly available exploit code, and impacts confidentiality, integrity, and availability of protected resources with low severity per CVSS 4.0 scoring (CVSS:5.5, AV:N/AC:L/PR:N/UI:N, VC:L/VI:L/VA:L). The vendor has not responded to early disclosure notification.

Technical ContextAI

YunaiV yudao-cloud is a Java-based microservices cloud framework built on Ruoyi-Vue-Pro architecture. The vulnerability resides in the JwtAuthenticationTokenFilter.java component, specifically in the doFilterInternal() method which is a Spring Security filter responsible for JWT token validation during HTTP request processing. The root cause (CWE-287: Improper Authentication) stems from insufficient validation logic that fails to properly verify or restrict the mock-token parameter, allowing attackers to craft authentication tokens that bypass the standard JWT signature and expiration validation. The filter likely treats mock-token values as trusted without cryptographic verification, enabling privilege escalation or unauthorized resource access.

Affected ProductsAI

YunaiV yudao-cloud versions up to and including 3.8.0 are affected, specifically the Ruoyi-Vue-Pro component running on Java/Spring Security frameworks. The CVE description does not specify minimum affected version, only upper bound. No CPE string was provided in the input data. Affected deployments include any yudao-cloud instance with the JwtAuthenticationTokenFilter.java component enabled and mock-token parameter processing active in the authentication pipeline.

RemediationAI

Upgrade YunaiV yudao-cloud to version 3.8.1 or later if available, or to the latest stable release to obtain patched JwtAuthenticationTokenFilter.java code that properly validates and sanitizes the mock-token parameter. If patch availability cannot be confirmed with the vendor due to their non-responsive stance, immediately disable or remove mock-token processing from the authentication filter by modifying JwtAuthenticationTokenFilter.java to reject any requests containing mock-token values, either by removing the parameter acceptance logic or by enforcing strict validation that only accepts cryptographically signed JWT tokens. As a compensating control, implement network-level authentication at the gateway/proxy layer (e.g., WAF rules blocking requests with mock-token parameter, or IP whitelisting) to prevent external access to the authentication endpoint, though this does not prevent internal threats. Apply Spring Security configuration hardening to enforce token signature validation regardless of parameter name, and audit all authentication filter overrides to ensure no other bypass mechanisms exist. Monitor authentication logs for mock-token usage patterns and block suspicious token values at the reverse proxy layer if available.