Quick answers
- Is CVE-2026-75411 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-75411 being exploited in the wild.
- How severe is CVE-2026-75411?
- Critical severity, with a CVSS score of 9.8, published 26 August 2026.
- Which products and versions are affected?
- JeecgBoot v3.9.2.
- Is there a fix for CVE-2026-75411?
- 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-75411 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-75411?
- Check whether you run JeecgBoot 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
The vulnerability is a blacklist bypass in Groovy script execution within the CodeNode component. The SecurityCheck class attempts to block dangerous calls such as Runtime.getRuntime(), Class.forName(), ProcessBuilder, and exec(), but Groovy's dynamic nature allows attackers to evade this through string concatenation (e.g., "Runtime".getRuntime()) and reflection-based method invocation (e.g., getMethod("ex"+"ec")). This enables arbitrary OS command execution. The attack requires authentication with the airag:flow:add permission; admin users have this permission by default. No official patch information is provided in the advisory.
Affected products
- JeecgBoot JeecgBoot v3.9.2
Timeline
- 2026-06-08: disclosed: Issue opened on GitHub
- 2026-08-26: advisory: Published to NVD as CVE-2026-75411