CVE-2026-44516: valtimo · Sensitive Data in Logs
Affects valtimoSource CVE Database V5
Not known to be exploited · CVSS 7.6 High : upgrade to 13.26.0 or 12.33.0 soon.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 13.26.0, 12.33.0
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 14 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade valtimo and web and valtimo-platform/valtimo to 13.26.0 or 12.33.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| valtimo-platformvaltimo | Affected
| Fixed in
|
| valtimo-platformvaltimo | Affected
| Fixed in
|
| com.ritense.valtimoweb | Affected
| Fixed in
|
| com.ritense.valtimoweb | Affected
| Fixed in
|
GitHubvaltimo-platform/valtimopkg:github/valtimo-platform/valtimoOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability is fixed in Valtimo versions 12.33.0 and 13.26.0. Users should upgrade to these or later versions to remediate the issue. No other official remediation or temporary fixes are indicated. Patch status is confirmed by the vendor advisory stating the fix is included in these versions.
Description
CVE-2026-44516 is a vulnerability in the Valtimo open-source business process automation platform affecting versions from 12.4.0 up to but not including 12.33.0, and from 13.0.0 up to but not including 13.26.0. The issue arises because the LoggingRestClientCustomizer component logs full HTTP request and response bodies and headers, including sensitive information, at the ERROR log level when an error response occurs.