CVE-2026-44516 json
Valtimo: Sensitive data exposure through HTTP request/response logging in LoggingRestClientCustomizer
published 2026-05-11 5 mo ago modified 2026-10-26 13 d ago also GHSA-3jh5-rr2q-xfv7 , EUVD-2026-30335
- cvss
- 7.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 9%
- public exploits
- 0
- none known
Summary
Valtimo is an open-source business process automation platform. From 12.4.0 to 12.33.0 and 13.26.0, the LoggingRestClientCustomizer in the web module automatically intercepts all outgoing HTTP calls made via Spring's RestClient and logs the full request body, response body, and response headers. When an error response is received, this information is included in the thrown HttpClientErrorException message, which is logged at ERROR level by Spring's default exception handling — regardless of the application's DEBUG log level setting. This vulnerability is fixed in 12.33.0 and 13.26.0.
Patch / fix
- maven com.ritense.valtimo:web 12.33.0, 13.26.0
- github.com/valtimo-platform/valtimo#599 pull request
- github.com/valtimo-platform/valtimo#600 pull request
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 5 mo ago
Exploit prediction
0.20% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.6 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:N |
| GitHub | 3.1 | 7.6 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | com.ritense.valtimo:web | >=12.4.0, <12.33.0 >=13.0.0, <13.26.0 |
12.33.0 13.26.0 |
Affected products
- valtimo-platform valtimo
- com.ritense.valtimo web
Classification
- Weakness
-
- CWE-532 Insertion of Sensitive Information into Log File
References
Sources
- CVE List CVE-2026-44516
- GitHub Advisory GHSA-3jh5-rr2q-xfv7
- NVD CVE-2026-44516
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.