---
id: CVE-2026-85260
title: >-
  Apache Camel: Camel-MLLP Protected Health Information Disclosure to Logs by
  Default
summary: >-
  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 …
severity: medium
cvss: 5.5
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'
cvssSource: cna
cwe:
  - CWE-532
vendor: Apache Software Foundation
product: 'org.apache.camel:camel-mllp'
affected:
  - 'org.apache.camel:camel-mllp >= 4.0.0 < 4.18.5'
  - 'org.apache.camel:camel-mllp >= 4.19.0 < 4.22.1'
published: '2026-10-19'
updated: '2026-10-19'
sourceUpdated: '2026-10-19T10:37:42.980Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-85260'
references:
  - url: 'https://camel.apache.org/security/CVE-2026-85260.html'
    label: Apache Camel Security Advisory - CVE-2026-85260
  - url: 'https://issues.apache.org/jira/browse/CAMEL-24454'
    label: CAMEL-24454
  - url: 'https://github.com/apache/camel/pull/25832'
    label: >-
      Fix on main, released in 4.23.0 (commit
      dd2bf57190c12ff7f1e97f121738867a680992ce)
  - url: 'https://github.com/apache/camel/pull/25944'
    label: >-
      Backport to camel-4.22.x, released in 4.22.1 (commit
      95b4c1500001bc32877df5b8fca0bc7bdd080666)
  - url: 'https://github.com/apache/camel/pull/25946'
    label: >-
      Backport to camel-4.18.x, released in 4.18.5 (commit
      4ec9b37d70b08c478966000fb1bd653abfe410e3)
tags:
  - cve.org
ingestedAt: '2026-10-19T12:27:23.811Z'
---

## Overview

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

- `org.apache.camel:camel-mllp >= 4.0.0 < 4.18.5`
- `org.apache.camel:camel-mllp >= 4.19.0 < 4.22.1`

## Remediation

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.

### Workarounds

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.