Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

GHSA-hfrg-mcvw-8mch

MEDIUM

GHSA-hfrg-mcvw-8mch is a medium-severity (CVSS 4.9) vulnerability in com.ritense.valtimo:inbox. O3 Security confirms whether GHSA-hfrg-mcvw-8mch is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Valtimo: Sensitive data exposure through inbox message logging in InboxHandlingService

Also known asCVE-2026-34164
Published
Apr 16, 2026
Updated
May 5, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

Blast Radius

1 pkg affected
com.ritense.valtimo:inbox

Real-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

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

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
Mavencom.ritense.valtimo:inbox13.0.0.RELEASE&&< 13.22.0.RELEASE13.22.0.RELEASE

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.ritense.valtimo:inbox. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update com.ritense.valtimo:inbox to 13.22.0.RELEASE or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hfrg-mcvw-8mch is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-hfrg-mcvw-8mch is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-hfrg-mcvw-8mch. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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` m
O3 Security · Impact-Aware SCA

Is GHSA-hfrg-mcvw-8mch in your dependencies?

O3 detects GHSA-hfrg-mcvw-8mch across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.