CVE-2026-36418
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 · uneditedJimuReport versions 2.3.4 and below are vulnerable to remote code execution due to improper handling of Aviator expressions. The /jmreport/executeSelectApi endpoint passes user-supplied input directly to the Aviator expression engine without adequate validation allowing attackers to execute arbitrary code.
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 confidenceJimuReport versions 2.3.4 and below are vulnerable to remote code execution due to the /jmreport/executeSelectApi endpoint passing user-supplied input directly to the Aviator expression engine without adequate validation, allowing attackers to execute arbitrary code.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
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 JimuReport installation and versionLocate the JimuReport JAR files (typically named jimu-report-*.jar) or check the application manifest/WAR file contents. Look for version information in filenames, pom.xml, or application.properties/yaml configuration files.Affected if The installed version is 2.3.4 or lower, or the version cannot be determined and the application uses JimuReport.
-
Verify the /jmreport/executeSelectApi endpoint existsReview the application web.xml or Spring MVC controller mappings to confirm the executeSelectApi endpoint is registered. For deployed applications, attempt a HEAD request to /jmreport/executeSelectApi or inspect the compiled bytecode for this route.Affected if The endpoint is present and exposed in the deployed application.
-
Confirm Aviator expression engine is in useSearch the application classpath for Aviator JAR files (aviator-*.jar) or inspect the codebase for imports of com.googlecode.aviator classes, particularly AviatorEvaluator or AviatorExpression.Affected if The Aviator expression engine library is included in the application runtime.
-
Check if the endpoint accepts user input without validationReview the source code or decompiled bytecode of the executeSelectApi controller. Look for direct passing of request parameters to Aviator evaluation methods (e.g., AviatorEvaluator.execute()) without sanitization or sandboxing logic.Affected if User-supplied parameters from the request are passed directly to Aviator evaluation without validation or sandboxing.
You are affected if JimuReport version 2.3.4 or lower is deployed AND the /jmreport/executeSelectApi endpoint is exposed AND Aviator expressions are evaluated with unsanitized user input.
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 input validation and sandboxing for Aviator expressions, or upgrade to a patched version if available, to prevent untrusted input from reaching the expression evaluation engine.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36418 — 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-36418 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