CVE-2026-10240
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 · uneditedA vulnerability was identified in JeecgBoot up to 3.9.2. The impacted element is an unknown function of the file /airag/airagModel/test. The manipulation of the argument baseUrl leads to server-side request forgery. The attack is possible to be carried out remotely. The exploit is publicly available and might be used. A fix is planned for the upcoming release.
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 · moderate confidenceServer-side request forgery (SSRF) vulnerability in JeecgBoot up to version 3.9.2. The /airag/airagModel/test endpoint accepts a baseUrl parameter that can be manipulated by attackers to force the server to make arbitrary requests to internal or external resources, potentially exposing sensitive internal services.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify JeecgBoot installation and versionLocate the JeecgBoot application and determine its version from pom.xml, application.yml, or the deployed WAR/JAR file's metadata. Compare the version number to the affected range (up to 3.9.2).Affected if The installed version is 3.9.2 or lower.
-
Locate the vulnerable endpointSearch the deployed application for the /airag/airagModel/test endpoint in the routing configuration, controller mappings, or by attempting to access it via HTTP (if permitted).Affected if The endpoint /airag/airagModel/test exists in the application.
-
Verify endpoint accepts baseUrl parameterInspect the controller source code for /airag/airagModel/test or test the endpoint by sending a request with a baseUrl parameter (e.g., GET /airag/airagModel/test?baseUrl=http://example.com).Affected if The endpoint accepts and processes a user-controllable baseUrl parameter.
-
Confirm endpoint accessibilityCheck if the /airag/airagModel/test endpoint is exposed without authentication or with weak authentication by examining the Spring Security configuration or testing direct access.Affected if The endpoint is accessible without proper authentication or network restrictions.
You are affected if JeecgBoot version 3.9.2 or lower is running and the /airag/airagModel/test endpoint is exposed with the baseUrl parameter accepted.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImplement strict allowlist-based input validation for the baseUrl parameter, restricting it to predefined, trusted domains or IP ranges only. Consider disabling or rate-limiting this endpoint until the official patch is applied.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10240 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-10240 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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