Live › vulnerability › CVE-2026-85260
Go to dashboardThe camel-mllp component writes HL7 clinical message content into application logs, because its logPhi option defaults to true and two code paths ignore the setting. An attacker or anyone with access to those logs can read patient health information.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Teams running Apache Camel with the camel-mllp component to receive or send HL7 messages, especially healthcare integrations. Any deployment on the affected version ranges that uses MLLP is exposed by default, because the logPhi option defaults to true. Deployments on fixed versions or without camel-mllp can skip it.
No product ranges from the sources yet.
mvn dependency:tree | grep camel-mllp, and compare it against the affected ranges: 4.0.0 to before 4.18.5, and 4.19.0 to before 4.22.1.camel-mllp endpoints and whether logPhi is set; if it is absent, the default of true applies.MSH| to confirm payload content is being written.4.23.0, or to 4.18.5 on the 4.18.x LTS line, or to 4.22.1 on the 4.22.x LTS line.logPhi=true explicitly only if the deployment relies on payload logging.logPhi=false, but note that two paths will still log payload content until the fix is applied, so restrict log access.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-85260")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.