CVE-2026-67926

This CVE describes a file parameter injection vulnerability achieving remote code execution in JeecgBoot's AI Chat Module, rated CVSS 9.8 (Critical). The EPSS score of 0.00208 suggests low observed exploitation—but treating that as evidence of safety would be a mistake. The critical gap between this CVE's headline severity and its actual exploitation probability reveals something important: the vulnerability exists in a component bolted onto an established low-code framework without commensurate threat modeling. JeecgBoot is mature (v3.9.2)—the core auth model was presumably hardened through iteration. The AI Chat Module represents a new trust boundary that wasn't baked into the original architecture. File parameter injection achieving RCE almost always traces back to one of two failures: either the developer didn't realize the parameter was user-controlled and reachable remotely, or they trusted input sanitization at a layer where trust was unwarranted. In a low-code context, the first failure is amplified because the abstraction layers between 'user uploads file' and 'server processes file' are hidden from the developer using the platform. They may have believed the AI module operated in a sandboxed context. The EPSS measures observed exploitation activity in the wild, which creates a temporal lag problem for new modules. A freshly shipped AI Chat Module doesn't yet have Shodan fingerprints or metasploit modules—its low EPSS may reflect that attackers haven't automated detection for it yet, not that it's legitimately contained. The CVSS measures potential; EPSS measures current attention. That's not a contradiction, it's a timeline. Compromising the AI Chat Module doesn't stay contained to the chat function. Low-code platforms run on shared state—shared authentication contexts, database connections, role mappings. You've punched through the one boundary that actually mattered: the platform's internal trust fabric. The vulnerability likely didn't invent new file handling code—it integrated with JeecgBoot's existing platform infrastructure written under different trust assumptions. The files parameter now reaches code paths that predate the AI module by years. The vulnerability isn't in the new bolt-on; it's in what the bolt-on activates from the platform's sediment layers. For defenders, two questions matter: Is the AI Chat Module's file endpoint actually internet-reachable in default deployments? And are there code paths the AI module reaches into that were written assuming internal-only access? Audit both. The EPSS may be low today, but the historical pattern from no-code RPA tool injection flaws through low-code workflow builder RCEs suggests this window of low exploitation is temporary.

Reviewed through automated stages and approved by a human before publication.