CVE-2026-36418
RCE in JimuReport <=2.3.4 via Aviator engine in executeSelectApi
Is CVE-2026-36418 being exploited?
Not confirmed. CVE-2026-36418 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.47% probability of exploitation in the next 30 days.
How severe is CVE-2026-36418?
CVE-2026-36418 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-36418?
Not known from our data. No patch reference has been recorded for CVE-2026-36418, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-36418 affect?
CVE-2026-36418 affects JimuReport <= 2.3.4. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-36418?
Upgrade when patch released; validate input and restrict API access
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
RCE via unvalidated Aviator expressions; attacker can execute code on server via /jmreport/executeSelectApi
Immediate action required