dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-10241

MEDIUM · 6.3 CVSS v3.1 Published 2026-06-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a Server-Side Request Forgery (SSRF) vulnerability in jeecgboot's Cloud Instance Metadata Endpoint. The flaw exists in the FileDownloadUtils.download2DiskFromNet function accessed via the /airag/app/debug endpoint, allowing remote attackers to make the server perform arbitrary HTTP requests to internal or external resources.

MitigationUpgrade jeecgboot to version 3.9.2 or later to remediate this SSRF vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify jeecgboot version
    Locate the jeecgboot JAR or WAR file and check its version metadata, typically found in the pom.xml, MANIFEST.MF, or version.properties file within the deployment package
    Affected if The installed version is earlier than 3.9.2 (e.g., 3.9.1, 3.8.x, 3.7.x, etc.)
  2. Confirm /airag/debug endpoint exists
    Check the application routing configuration or web.xml for mappings to /airag/app/debug, or attempt a HEAD request to the endpoint if it is network-accessible
    Affected if The /airag/app/debug endpoint is registered and exposed in the application routing
  3. Verify FileDownloadUtils is present
    Inspect the compiled classpath for the FileDownloadUtils class, typically located in the jeecg-cloud-common or similar core module JAR, and confirm the download2DiskFromNet method exists
    Affected if The FileDownloadUtils class with the download2DiskFromNet method is present in the deployed codebase
  4. Check network exposure of admin endpoints
    Review firewall rules, reverse proxy configuration, or API gateway settings to determine whether the /airag/* paths are reachable from untrusted networks
    Affected if The /airag/app/debug endpoint is accessible from the internet or untrusted internal networks without authentication filtering
  5. Review access controls on /airag paths
    Examine Spring Security or equivalent filter chain configuration files (e.g., securityConfig.java) to see if /airag/app/debug is explicitly excluded from authentication requirements
    Affected if The /airag/app/debug endpoint is mapped without requiring authentication or is explicitly permitted in security bypass rules

The environment is affected if jeecgboot version is earlier than 3.9.2 AND the /airag/app/debug endpoint is accessible without proper authentication or network restrictions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade jeecgboot to version 3.9.2 or later to remediate this SSRF vulnerability.

Recommended fix High confidence

3.9.2

  1. 1. Back up the current jeecgboot installation and database
  2. 2. Download jeecgboot version 3.9.2 from the official jeecgboot repository or release channel
  3. 3. Upgrade the jeecgboot installation to version 3.9.2 following the standard upgrade documentation
  4. 4. Verify the upgrade was successful and the FileDownloadUtils.download2DiskFromNet function is now patched
  5. 5. Test that the /airag/app/debug endpoint no longer processes untrusted URLs

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10241 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-10241 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data