---
id: "CVE-2026-85260"
kind: "vulnerability"
aliases: ["CVE-2026-85260"]
title: "Apache Camel MLLP logs patient HL7 data by default"
severity: "medium"
cvss: 5.5
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["apache-camel", "camel-mllp", "healthcare", "hl7", "java", "package"]
not_affected_if: ["fixed-version", "logs-restricted", "no-mllp"]
published_at: "2026-10-19T11:17:23+00:00"
first_seen_at: "2026-10-23T21:57:18+00:00"
updated_at: "2026-10-25T04:12:52+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-85260", "first_seen_at": "2026-10-23T21:57:18+00:00"}]
---

# Apache Camel MLLP logs patient HL7 data by default

The 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, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the Apache Camel version in the project build file or `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.
- Search the application configuration and routes for `camel-mllp` endpoints and whether `logPhi` is set; if it is absent, the default of true applies.
- Inspect application logs for HL7 segments such as `MSH|` to confirm payload content is being written.

## Fix

- Upgrade Apache Camel to `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.
- After upgrading, set `logPhi=true` explicitly only if the deployment relies on payload logging.
- If you cannot upgrade yet, set `logPhi=false`, but note that two paths will still log payload content until the fix is applied, so restrict log access.

## Timeline

- 2026-10-23T21:57:18+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-85260

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_