AntFlow CVE-2026-75414

Exploitation requires that the vulnerable ActivitiTest.java expression-evaluation endpoint of AntFlow V2.0.0 be deployed and network-reachable by the attacker; the description characterizes it as a front-desk (pre-authentication) path and CVSS PR:N/UI:N indicates no credentials or user interaction are needed against a default-reachable instance. The concrete prerequisite is that user-controlled input reaches the JUEL expression evaluator unfiltered. The main limiting factor is exposure: if this endpoint is a test-only component that is not shipped, not routed, or is restricted behind authentication/network controls in a given deployment, remote unauthenticated exploitation is not possible.

The signals are mixed: the CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N, full C/I/A impact) and CWE-94 unauthenticated RCE point to a critical, easily automatable flaw, and a public exploit write-up lowers the barrier to weaponization; any organization running AntFlow V2.0.0 with the test/expression endpoint reachable should treat this as urgent, since expression-injection-to-command-execution is straightforward to script. Counterbalancing this, EPSS is only 0.17% (7th percentile) and there is no CISA KEV listing, which suggests real-world exploitation is currently targeted or negligible rather than mass-scanned - consistent with AntFlow's small deployment footprint rather than with the flaw being hard to exploit. The dominant uncertainty is exposure: if the vulnerable ActivitiTest path is a developer/test artifact not shipped or not routed in production, real risk drops sharply, so confirm whether the endpoint is reachable in your build before prioritizing purely on the 9.8.

An unauthenticated attacker sends an HTTP request to the AntFlow front-desk ActivitiTest endpoint containing a crafted JUEL expression (e.g. one that resolves to a Java runtime call). Because the input is evaluated without filtering, the expression executes and runs an arbitrary OS command on the server, giving the attacker code execution. A public write-up demonstrating this 'front desk command execution' already exists, reducing the effort required.