CVE-2026-85260: Apache Camel: Camel-MLLP Protected Health Information Disclosure to Logs by Default
Insertion of Sensitive Information into Log File vulnerability in Apache Camel MLLP component.
This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.
The camel-mllp component carries a logPhi option that governs whether HL7 payload content may be written to the log. It defaulted to true, so a deployment that did nothing logged protected health information out of the box. Two further paths wrote payload content to the log regardless of the setting, so even an operator who had turned logPhi off was still exposed on those paths. MLLP is used to carry HL7 clinical messages, so the content concerned is patient data, and it reached ordinary application logs where it is subject to whatever retention, aggregation and access the deployment applies to logs generally rather than to clinical records.
Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. logPhi now defaults to false and is honoured on the paths that previously ignored it. This is a changed default: a deployment that relied on payload logging must now set logPhi=true explicitly. Because the upgrade guide for a change like this lives on the main branch only, operators upgrading within the 4.18.x or 4.22.x lines should treat this advisory as the notice of that change. For deployments that cannot upgrade immediately, set logPhi=false and be aware that two paths will continue to log payload content until the fix is applied; restrict access to the logs accordingly.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Apache Camelto a version that resolves this vulnerability.Fixed in 4.23.0 - Upgrade
Upgrade
Apache Camelto a version that resolves this vulnerability.Fixed in 4.18.5 - Upgrade
Upgrade
Apache Camelto a version that resolves this vulnerability.Fixed in 4.22.1 - Configuration
Set logPhi=false for deployments that cannot upgrade immediately; it now defaults to false and is honored on the paths that previously ignored it. Deployments that intentionally require payload logging must set logPhi=true explicitly.
Apache Camel camel-mllp logPhi = false - Compensating control
Restrict access to application logs because two paths continue to log payload content when logPhi=false until the fix is applied.
Event History
Frequently Asked Questions
Which deployments are exposed?
Deployments using the Apache Camel MLLP component in versions 4.0.0 through before 4.18.5, or 4.19.0 through before 4.22.1, are affected. MLLP deployments handling HL7 clinical messages are exposed to patient data being written to ordinary application logs.
Does disabling logPhi fully mitigate the issue in affected releases?
No. Although logPhi controlled payload logging, two paths logged payload content regardless of its setting, so deployments with logPhi disabled could still disclose protected health information.
What should teams do if they rely on HL7 payload logging?
Upgrade to Apache Camel 4.23.0, or to 4.18.5 on the 4.18.x LTS stream or 4.22.1 on the 4.22.x LTS stream. After upgrading, payload logging is disabled by default; deployments that intentionally require it must explicitly set logPhi=true.
How can an organization determine whether data may already have been exposed?
Review ordinary application logs and any systems that retain, aggregate, or grant access to those logs for HL7 payload content or patient data. This is particularly important for affected deployments that left logPhi at its default, because it defaulted to true.