Valtimo: Sensitive data exposure through inbox message logging in InboxHandlingService

Exploitation

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

CVSS

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

EPSS

• CVE-2026-34164: 0.37% estimated exploitation activity in the next 30 days; percentile 30.55 (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 InboxHandlingService logs the full content of every incoming inbox message at INFO level (logger.info("Received message: {}", message)). Inbox messages are wrappers around outbox message data, which can contain highly sensitive information such as personal data (PII), citizen identifiers (BSN), and case details. Impact This data is exposed to: - Anyone with access to application logs (stdout/log files) - Any Valtimo user with the admin role, through the logging module in the Admin UI Affected Code com.ritense.inbox.InboxHandlingService#handle in the inbox module. Resolution Fixed in 13.22.0 via commit f16a1940ba (PR #497, tracking issue gzac-issues#653). The log statement was downgraded from INFO to DEBUG and the message payload was removed from the log output. Mitigation For versions before 13.22.0, consider: - Restricting access to application logs - Adjusting the log level for com.ritense.inbox to WARN or higher in your application configuration

Published by the source

16 Apr 2026, 20:42 UTC

Last modified by the source

24 Apr 2026, 20:36 UTC

Source last checked

26 Oct 2026, 16:45 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-hfrg-mcvw-8mch

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

# Patch Next advisory brief: CVE-2026-34164

Advisory: Valtimo: Sensitive data exposure through inbox message logging in InboxHandlingService
IDs: CVE-2026-34164, GHSA-hfrg-mcvw-8mch
Record: https://patchnext.com/advisories/cve-2026-34164 (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: Medium (CVSS 4.9)
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:inbox 13.22.0.RELEASE. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.ritense.valtimo:inbox: affected >= 13.0.0.RELEASE, < 13.22.0.RELEASE; fixed in 13.22.0.RELEASE

## Suggested inspection (read-only)
- Maven com.ritense.valtimo:inbox: 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:inbox.
- 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-hfrg-mcvw-8mch (GitHub-reviewed advisory GHSA-hfrg-mcvw-8mch lists affected ranges: Maven com.ritense.valtimo:inbox >=13.0.0.RELEASE <13.22.0.RELEASE)

Commands are suggestions: review each one before running it.