Valtimo has sensitive data exposure through HTTP request/response logging in LoggingRestClientCustomizer

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.6 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:N

EPSS

• CVE-2026-44516: 0.20% estimated exploitation activity in the next 30 days; percentile 9.86 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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. Impact The logged data can contain highly sensitive information including: - Authentication credentials (JWT tokens, API keys, OAuth tokens) in request bodies or response headers - Personal data (BSN, email addresses, case details) in request/response bodies - Session tokens in Set-Cookie response headers This data is exposed to: - Anyone with access to application logs (stdout/log files) - Users with access to logging aggregation tools (e.g. Grafana/Loki) - Any Valtimo user with the admin role, through the built-in logging module (since Valtimo…

Published by the source

11 May 2026, 16:11 UTC

Last modified by the source

14 May 2026, 20:54 UTC

Source last checked

26 Oct 2026, 16:45 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-3jh5-rr2q-xfv7

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-44516

Advisory: Valtimo has sensitive data exposure through HTTP request/response logging in LoggingRestClientCustomizer
IDs: CVE-2026-44516, GHSA-3jh5-rr2q-xfv7
Record: https://patchnext.com/advisories/cve-2026-44516 (revision 1, source checked 26 Oct 2026, 16:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.ritense.valtimo:web 13.26.0, 12.33.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.ritense.valtimo:web: affected >= 12.4.0, < 12.33.0; >= 13.0.0, < 13.26.0; fixed in 13.26.0, 12.33.0

## Suggested inspection (read-only)
- Maven com.ritense.valtimo:web: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.ritense.valtimo:web.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-3jh5-rr2q-xfv7 (GitHub-reviewed advisory GHSA-3jh5-rr2q-xfv7 lists affected ranges: Maven com.ritense.valtimo:web >=12.4.0 =13.0.0 <13.26.0)

Commands are suggestions: review each one before running it.