CVE-2026-42555
CRITICALCVE-2026-42555 is a critical-severity (CVSS 9.1) remote code execution vulnerability in com.ritense.valtimo:document. O3 Security confirms whether CVE-2026-42555 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Valtimo: SpEL injection via StandardEvaluationContext allows Remote Code Execution by admin users
Blast Radius
com.ritense.valtimo:document☕com.ritense.valtimo:case☕com.ritense.valtimo:contractReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Valtimo is an open-source business process automation platform. com.ritense.valtimo:document from 12.0.0 to before 12.32.0, com.ritense.valtimo:case from 13.0.0 to before 13.23.0, and com.ritense.valtimo:contract from 13.4.0 to before 13.23.0 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. This vulnerability is fixed in com.ritense.valtimo:document 2.32.0, com.ritense.valtimo:case 13.23.0, and com.ritense.valtimo:contract 13.23.0.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.ritense.valtimo:document | ≥ 12.0.0&&< 12.32.0 | 12.32.0 |
| ☕Maven | com.ritense.valtimo:case | ≥ 13.0.0&&< 13.23.0 | 13.23.0 |
| ☕Maven | com.ritense.valtimo:contract | ≥ 13.4.0&&< 13.23.0 | 13.23.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.ritense.valtimo:document. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update com.ritense.valtimo:document to 12.32.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-42555 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-42555 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2026-42555. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-42555 in your dependencies?
O3 detects CVE-2026-42555 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.