# CVE-2026-7604: JeecgBoot OpenApi Service OpenApiController.java OpenApiController.call server-side request forgery

> Remote attackers can exploit a server-side request forgery vulnerability in JeecgBoot's OpenApi Service to access internal resources or bypass security controls.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **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:** 2 May 2026
- **Updated:** 4 May 2026
- **Also known as:** GHSA-fc85-mqvw-fgvh

## What is CVE-2026-7604?

CVE-2026-7604 is a medium-severity server-side request forgery vulnerability in JeecgBoot, published on 2 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was identified in JeecgBoot up to 3.9.1. This affects the function OpenApiController.add/OpenApiController.call of the file OpenApiController.java of the component OpenApi Service. Such manipulation of the argument originUrl database leads to server-side request forgery. It is possible to launch the attack remotely. The exploit is publicly available and might be used. It is suggested to upgrade the affected component. The vendor confirmed the issue and will provide a fix in the upcoming release.

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

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


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

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

## Is CVE-2026-7604 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7604 is a medium-severity server-side request forgery vulnerability in JeecgBoot, published on 2 May 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-7604 exists.

Affected product: JeecgBoot. 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-7604/ (Markdown: https://insights.sbomify.com/CVE-2026-7604/index.md)
```

## Sources

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

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