CVE-2026-42555

Multiple classes evaluate Spring Expression Language (SpEL) expressions from user-supplied input using StandardEvaluationContext, which provides unrestricted access to Java types and methods. An authenticated user with the ADMIN role can achieve Remote Code Execution and credential exfiltration.

Affected Components

1. DocumentMigrationService (since 12.0.0)

Exploitable through the document migration REST API:

• POST /api/management/v1/document-definition/migrate
• POST /api/management/v1/document-definition/migration/conflicts

The malicious SpEL expression is supplied in the source or target field of a DocumentMigrationPatch object in the request body, using the ${...} template syntax.

• In 12.x: com.ritense.document.service.DocumentMigrationService#handleSpelExpression (document module)
• In 13.x: same class, moved to the case module

2. Condition (since 13.4.0)

Exploitable through any admin-configured widget, dashboard, or feature that uses the Condition framework. The SpEL expression is supplied in the value field of a condition's JSON configuration.

• com.ritense.valtimo.contract.conditions.Condition#resolveValue (contract module)

This component has a significantly wider attack surface than DocumentMigrationService, as conditions are used across many modules.

An attacker with ADMIN credentials can:

• Execute arbitrary OS commands via T(java.lang.Runtime).getRuntime().exec('...')
• Exfiltrate all environment variables (database passwords, API keys, Keycloak secrets) via T(java.lang.System).getenv()
• Read JVM system properties via T(java.lang.System).getProperties()
• Load arbitrary classes via T(java.lang.Class).forName('...')

Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.

CVE-2026-42555 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.32.0, 13.23.0); upgrading removes the vulnerable code path.

Kodem intelligence

Replace StandardEvaluationContext with SimpleEvaluationContext in both affected classes, which disallows Java type references and arbitrary method invocation:

val evaluationContext = SimpleEvaluationContext
    .forPropertyAccessors(MapAccessor(), jsonPropertyAccessor)
    .build()

1. What is CVE-2026-42555? CVE-2026-42555 is a critical-severity code injection vulnerability in com.ritense.valtimo:document (maven), affecting versions >= 12.0.0, < 12.32.0. It is fixed in 12.32.0, 13.23.0. Untrusted input is evaluated as executable code within the application's runtime environment.
2. How severe is CVE-2026-42555? CVE-2026-42555 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 packages are affected by CVE-2026-42555?
   • com.ritense.valtimo:document (maven) (versions >= 12.0.0, < 12.32.0)
   • com.ritense.valtimo:case (maven) (versions >= 13.0.0, < 13.23.0)
   • com.ritense.valtimo:contract (maven) (versions >= 13.4.0, < 13.23.0)
4. Is there a fix for CVE-2026-42555? Yes. CVE-2026-42555 is fixed in 12.32.0, 13.23.0. Upgrade to this version or later.
5. Is CVE-2026-42555 exploitable, and should I be worried? Whether CVE-2026-42555 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-2026-42555 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-2026-42555?
   • Upgrade com.ritense.valtimo:document to 12.32.0 or later
   • Upgrade com.ritense.valtimo:case to 13.23.0 or later
   • Upgrade com.ritense.valtimo:contract to 13.23.0 or later