CVE-2025-58059

Attack requirements

The following conditions have to be met in order to perform this attack:

• The user must be logged in
• The user must have the admin role (ROLE_ADMIN), which is required to change process definitions
• The user must have some knowledge about running scripts via a the Camunda/Operator engine

Workarounds

If no scripting is needed in any of the processes, it could be possible to disable it altogether via the ProcessEngineConfiguration:

@Component
class NoScriptEnginePlugin : ProcessEnginePlugin {
    override fun preInit(processEngineConfiguration: ProcessEngineConfigurationImpl) {}

    override fun postInit(processEngineConfiguration: ProcessEngineConfigurationImpl) {
        processEngineConfiguration.scriptEngineResolver = null
    }

    override fun postProcessEngineBuild(processEngine: ProcessEngine) {}
}

Warning: this workaround could lead to unexpected side-effects. Please test thoroughly.

References

• Valtimo 12 and lower: Camunda Scripting
• Valtimo 13 and higher: Operaton Scripting

Any admin that can create or modify and execute process-definitions could gain access to sensitive data or resources.

This includes but is not limited to:

• Running executables on the application host
• Inspecting and extracting data from the host environment or application properties
• Spring beans (application context, database pooling)

Untrusted input reaches a shell command, allowing arbitrary commands to run on the host. Typical impact: code execution in the application's environment.

CVE-2025-58059 has a CVSS score of 9.1 (Critical). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (12.16.0.RELEASE, 13.1.2.RELEASE); upgrading removes the vulnerable code path.

Kodem intelligence

Version 12.16.0 and 13.1.2 have been patched. It is strongly advised to upgrade.

1. What is CVE-2025-58059? CVE-2025-58059 is a critical-severity OS command injection vulnerability in com.ritense.valtimo:core (maven), affecting versions < 12.16.0.RELEASE. It is fixed in 12.16.0.RELEASE, 13.1.2.RELEASE. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
2. How severe is CVE-2025-58059? CVE-2025-58059 has a CVSS score of 9.1 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of com.ritense.valtimo:core are affected by CVE-2025-58059? com.ritense.valtimo:core (maven) versions < 12.16.0.RELEASE is affected.
4. Is there a fix for CVE-2025-58059? Yes. CVE-2025-58059 is fixed in 12.16.0.RELEASE, 13.1.2.RELEASE. Upgrade to this version or later.
5. Is CVE-2025-58059 exploitable, and should I be worried? Whether CVE-2025-58059 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-58059 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-58059?
   • Upgrade com.ritense.valtimo:core to 12.16.0.RELEASE or later
   • Upgrade com.ritense.valtimo:core to 13.1.2.RELEASE or later