# CVE-2026-10241: Server-side request forgery in The server processes these URLs

> Remote attackers can exploit a server-side request forgery flaw in JeecgBoot to access internal cloud metadata endpoints and sensitive data.

- **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:** 1 Jun 2026
- **Updated:** 1 Jun 2026
- **Also known as:** GHSA-3m2m-6phq-rxrq

## What is CVE-2026-10241?

CVE-2026-10241 is a medium-severity server-side request forgery vulnerability in jeecgboot The server processes these URLs, published on 1 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security flaw has been discovered in jeecgboot The server processes these URLs up to 3.9.1. This affects the function FileDownloadUtils.download2DiskFromNet of the file /airag/app/debug of the component Cloud Instance Metadata Endpoint. The manipulation results in server-side request forgery. The attack may be performed from remote. The exploit has been released to the public and may be used for attacks. Upgrading to version 3.9.2 mitigates this issue. It is suggested to upgrade the affected component.

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

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


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

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

## Is CVE-2026-10241 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10241 is a medium-severity server-side request forgery vulnerability in jeecgboot The server processes these URLs, published on 1 Jun 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-10241 exists.

Affected product: jeecgboot The server processes these URLs. 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-10241/ (Markdown: https://insights.sbomify.com/CVE-2026-10241/index.md)
```

## Sources

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

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