CVE-2026-7710
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe JWT authentication filter (JwtAuthenticationTokenFilter.java) in yudao-cloud/RuoYi-Vue-Pro contains an authentication bypass vulnerability where manipulating a 'mock-token' parameter allows unauthorized access. This indicates a flaw in token validation logic that accepts a test or debug token without proper verification.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the JWT authentication filter fileSearch for JwtAuthenticationTokenFilter.java in the application's source code repository or deployment directoryAffected if The file exists and contains mock-token or mockToken parameter handling logic
-
Inspect token validation logicExamine the JwtAuthenticationTokenFilter.java code for any code branches that accept tokens without signature verification, particularly those labeled as mock, test, or debug tokensAffected if The filter contains logic that accepts mock-token parameter values without proper signature/expiration validation
-
Check for mock-token parameter processingReview HTTP request handling code to see if a 'mock-token' parameter is being read and used for authentication without proper validationAffected if The application processes a mock-token parameter from requests and uses it directly for authentication without rejecting non-production tokens
-
Verify token bypass conditionLook for conditional logic that skips token validation when a specific parameter or header is present (e.g., checking for test/debug flags)Affected if There is conditional logic that bypasses normal JWT validation when mock-token or similar debug functionality is triggered
-
Confirm affected deploymentIdentify if the deployed yudao-cloud or RuoYi-Vue-Pro application has the vulnerable JWT filter activeAffected if The application uses JwtAuthenticationTokenFilter from yudao-cloud/RuoYi-Vue-Pro and has mock-token handling enabled
A user is affected if their yudao-cloud/RuoYi-Vue-Pro deployment contains the JwtAuthenticationTokenFilter with mock-token parameter handling that bypasses proper JWT signature and expiration validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImmediately review and disable any mock/test token functionality in the JWT filter, implement proper token signature and expiration validation, and restrict the filter to reject non-production tokens. Consider deploying a WAF rule to block mock-token parameter abuse until a code fix is applied.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7710 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-7710 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data