# CVE-2026-116007: A flaw has been found in YunaiV/zhijiantianya ruoyi-vue-pro up to 2026.09.


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 25 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-529h-x3v3-53h3

## What is CVE-2026-116007?

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

### Official description

A flaw has been found in YunaiV/zhijiantianya ruoyi-vue-pro up to 2026.09. The impacted element is the function SmsCodeServiceImpl.validateSmsCode0 of the file /service/sms/SmsCodeServiceImpl.java of the component SMS Code Verification. This manipulation causes improper restriction of excessive authentication attempts. The attack may be initiated remotely. The complexity of an attack is rather high. The exploitability is regarded as difficult. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-799 (Improper Control of Interaction Frequency), CWE-307 (Improper Restriction of Excessive Authentication Attempts)

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


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

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

## Is CVE-2026-116007 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116007 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-116007 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-116007/ (Markdown: https://insights.sbomify.com/CVE-2026-116007/index.md)
```

## Sources

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

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