# CVE-2026-110610: ruoyi-vue-pro through 2026.09 SSRF via Midjourney referImageUrl and notify imageUrl

> Authenticated attackers can exploit SSRF in the AI image service to access internal network resources and cloud metadata endpoints.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-v372-v7rj-cgvj

## What is CVE-2026-110610?

CVE-2026-110610 is a medium-severity server-side request forgery vulnerability in YunaiV ruoyi-vue-pro, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ruoyi-vue-pro through 2026.09 contains a server-side request forgery vulnerability in the yudao-module-ai image service that allows authenticated users to make the server fetch arbitrary URLs by supplying referImageUrl to the midjourney imagine endpoint. Attackers can force Hutool HttpUtil.downloadBytes() requests to loopback, private, or cloud metadata addresses to probe internal-only HTTP services and reach metadata endpoints.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-110610 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110610 is a medium-severity server-side request forgery vulnerability in YunaiV ruoyi-vue-pro, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-110610 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-110610/ (Markdown: https://insights.sbomify.com/CVE-2026-110610/index.md)
```

## Sources

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

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