CVE-2026-42555 — document
CRITICALCVE-2026-42555 is a critical-severity (CVSS 9.1) Code Injection vulnerability in com.ritense.valtimo:document. A fix is available for com.ritense.valtimo:document — see the affected versions and patch details below.
Valtimo: SpEL injection via StandardEvaluationContext allows Remote Code Execution by admin users
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-42555.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2026-42555 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
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
Summary
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.
Impact
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('...')
Affected Components
1. DocumentMigrationService (since 12.0.0)
Exploitable through the document migration REST API:
POST /api/management/v1/document-definition/migratePOST /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.
Remediation
Replace StandardEvaluationContext with SimpleEvaluationContext in both affected classes, which disallows Java type references and arbitrary method invocation:
val evaluationContext = SimpleEvaluationContext
.forPropertyAccessors(MapAccessor(), jsonPropertyAccessor)
.build()
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.ritense.valtimo:document | ≥ 12.0.0&&< 12.32.0 | 12.32.0com.ritense.valtimo:document:12.32.0 |
| ☕Maven | com.ritense.valtimo:case | ≥ 13.0.0&&< 13.23.0 | 13.23.0com.ritense.valtimo:case:13.23.0 |
| ☕Maven | com.ritense.valtimo:contract | ≥ 13.4.0&&< 13.23.0 | 13.23.0com.ritense.valtimo:contract: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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-42555 can be triaged on real exposure rather than presence alone.
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 Security finds CVE-2026-42555 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.