Quick answers
- Is CVE-2026-36418 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-36418 being exploited in the wild.
- How severe is CVE-2026-36418?
- Critical severity, with a CVSS score of 9.1, published 17 June 2026.
- Which products and versions are affected?
- JeecgBoot JimuReport <= 2.3.4.
- Is there a fix for CVE-2026-36418?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-36418 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-36418?
- Check whether you run JeecgBoot JimuReport at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A remote code execution (RCE) vulnerability exists in JimuReport versions 2.3.4 and earlier due to an expression injection flaw. The root cause is located in the /jmreport/executeSelectApi endpoint, which accepts user-supplied input and passes it directly to the Aviator expression engine's execute method without sufficient validation or sandboxing. A remote, unauthenticated attacker can exploit this by submitting malicious Aviator expressions via a network request, leading to arbitrary code execution on the underlying host. The vulnerability is classified as CWE-94 (Improper Control of Generation of Code).
Affected products
- JeecgBoot JimuReport <= 2.3.4
Timeline
- 2026-06-17: disclosed
- 2026-06-17: advisory