# CVE-2026-116006: YunaiV/zhijiantianya ruoyi-vue-pro SMS Code Verification AuthController.java improper authentication


- **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
- **Fix available:** No
- **Published:** 25 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-jwvr-26h4-vc23

## What is CVE-2026-116006?

CVE-2026-116006 is a medium-severity vulnerability in YunaiV ruoyi-vue-pro, published on 25 Oct 2026. 

### Official description

A vulnerability was detected in YunaiV/zhijiantianya ruoyi-vue-pro up to 2026.09. The affected element is an unknown function of the file AuthController.java of the component SMS Code Verification. The manipulation of the argument mobile/code results in improper authentication. The attack can be launched remotely. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-116006 being exploited?

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

Public exploit code:

- Ruoyi-Vue-Pro - Unauthenticated Admin Takeover via Predictable SMS Code (nuclei): http/cves/2026/CVE-2026-116006.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116006 is a medium-severity vulnerability in YunaiV ruoyi-vue-pro, published on 25 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-116006 exists.

Affected product: YunaiV ruoyi-vue-pro. 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-116006/ (Markdown: https://insights.sbomify.com/CVE-2026-116006/index.md)
```

## Sources

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

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