{"answers":{"affected":"2 open source packages ship an affected version, including com.ritense.valtimo:inbox.","exploited":"There is no known exploitation of CVE-2026-34164 in the wild and no public exploit code.","fix":"Upgrade com.ritense.valtimo:inbox to 13.22.0.RELEASE or later.","what":"CVE-2026-34164 is a medium-severity vulnerability in valtimo-platform valtimo, published on 16 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-34164 and fix it if it is affected.\n\nWhat it is: CVE-2026-34164 is a medium-severity vulnerability in valtimo-platform valtimo, published on 16 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-34164 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- com.ritense.valtimo:inbox (Maven): affected from 13.0.0.RELEASE; fixed in 13.22.0.RELEASE\n- com.ritense.valtimo:inbox (Maven): affected from 13.0.0.RELEASE; fixed in 13.22.0.RELEASE\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-34164/ (Markdown: https://insights.sbomify.com/CVE-2026-34164/index.md)","id":"CVE-2026-34164","markdown":"https://insights.sbomify.com/CVE-2026-34164/index.md","name":"CVE-2026-34164","record":{"aliases":["GHSA-hfrg-mcvw-8mch"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Business process automation","requires_auth":"high_privilege","summary":"Attackers with log access can view sensitive PII and case details exposed in application logs by the InboxHandlingService.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"Valtimo is an open-source business process automation platform. In versions 13.0.0 through 13.21.0, the InboxHandlingService logs the full content of every incoming inbox message at INFO level. Inbox messages can contain highly sensitive information including personal data (PII), citizen identifiers (BSN), and case details. This data is exposed to anyone with access to application logs or any Valtimo user with the admin role through the Admin UI logging module. This issue has been fixed in version 13.22.0. If developers are unable to upgrade immediately, they can restrict access to application logs and adjust the log level for com.ritense.inbox to WARN or higher in their application configuration as a workaround.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Valtimo: Sensitive data exposure through inbox message logging in InboxHandlingService","id":"CVE-2026-34164","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":5,"next":{"headline":"go-git: Maliciously crafted idx file can cause asymmetric memory consumption","id":"CVE-2026-34165"},"packages":[{"ecosystem":"Maven","fixed":["13.22.0.RELEASE"],"introduced":["13.0.0.RELEASE"],"last_affected":[],"package":"com.ritense.valtimo:inbox","purl":null,"source":"GHSA-hfrg-mcvw-8mch"},{"ecosystem":"Maven","fixed":["13.22.0.RELEASE"],"introduced":["13.0.0.RELEASE"],"last_affected":[],"package":"com.ritense.valtimo:inbox","purl":"pkg:maven/com.ritense.valtimo/inbox","source":"GHSA-hfrg-mcvw-8mch"}],"prev":{"headline":"Server-Side Request Forgery via MCP Tools Endpoint in FastGPT","id":"CVE-2026-34163"},"products":["valtimo"],"published":"2026-04-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-18","vendors":["valtimo-platform"]},"summary":"Attackers with log access can view sensitive PII and case details exposed in application logs by the InboxHandlingService.","url":"https://insights.sbomify.com/CVE-2026-34164/"}