CVE-2026-85260: Apache Camel: Camel-MLLP Protected Health Information Disclosure to Logs by Default

Is it exploited?

Not on CISA's list. CISA has not added it to the Known Exploited Vulnerabilities catalog as of 29 Oct 2026. If CISA adds it, this page shows it as known exploited.

How likely is exploitation in the next 30 days?

0.2%

EPSS score, percentile 7.5 of all scored records. A probability estimated by FIRST, not a report of exploitation.

How severe?

5.5 Medium

CVSS v3.1 base score, given by the CNA

What should I do?

Upgrade to Apache Camel 4.23.0, which fixes the issue. Full textSolution from the CVE record.

CISA has set no required action, because the vulnerability is not in KEV.

Advisories and patches (4)

Which versions are affected?

Affected

• from 4.0.0 to before 4.18.5
• from 4.19.0 to before 4.22.1

Unaffected 4.18.5; 4.22.1; 4.23.0

Versions by product

Source: CISA KEV 2026.10.29, as of 29 Oct 2026; FIRST EPSS, as of 29 Oct 2026; CVE List, as of 29 Oct 2026. About the data.

What to do

Solution (from the CVE record)

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.

Workaround (from the CVE record)

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.

Advisories and patches

• Fix on main, released in 4.23.0 (commit dd2bf57190c12ff7f1e97f121738867a680992ce) (Patch)
• Backport to camel-4.22.x, released in 4.22.1 (commit 95b4c1500001bc32877df5b8fca0bc7bdd080666) (Patch)
• Backport to camel-4.18.x, released in 4.18.5 (commit 4ec9b37d70b08c478966000fb1bd653abfe410e3) (Patch)
• Apache Camel Security Advisory - CVE-2026-85260 (Vendor advisory)

This summary is based on the CVE record as of 29 Oct 2026. Check the vendor's advisory before you act: affected versions and fixes can change.

Affected products and versions

As listed in the CVE record.

Versions not listed are: unaffected.

Versions the record lists as unaffected: 4.18.5, 4.22.1, 4.23.0.

Source: CVE List, as of 29 Oct 2026. About the data.

About this vulnerability

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 t…

Summary: CVE record, as of 29 Oct 2026.

• CISA has not added CVE-2026-85260 to its Known Exploited Vulnerabilities (KEV) catalog, as of 29 Oct 2026.
• The CVE record was published on 19 Oct 2026.
• The CVE record carries a CVSS v3.1 base score of 5.5 (Medium), given by its CNA.
• FIRST's EPSS model puts the probability of exploitation in the next 30 days at 0.2% (percentile 7.5), as of 29 Oct 2026. EPSS is a statistical estimate, not a report of exploitation.
• CISA's SSVC assessment in the CVE record: exploitation none, automatable no, technical impact partial.
• The credits in the CVE record name Anthropic (Claude) as finder.

Source: CISA KEV 2026.10.29, as of 29 Oct 2026; CVE List, as of 29 Oct 2026; FIRST EPSS, as of 29 Oct 2026. About the data.

Description

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.

Source: CVE List, as of 29 Oct 2026. About the data.

Timeline

Known exploited Apache vulnerabilities

• CVE-2016-3081: Apache Struts Command Injection Vulnerability (added 8 Oct 2026)
• CVE-2026-34486: Apache Tomcat Missing Encryption of Sensitive Data Vulnerability (added 4 Aug 2026)
• CVE-2026-34197: Apache ActiveMQ Improper Input Validation Vulnerability (added 16 Apr 2026)
• CVE-2024-38475: Apache HTTP Server Improper Escaping of Output Vulnerability (added 1 May 2025)
• CVE-2025-24813: Apache Tomcat Path Equivalence Vulnerability (added 1 Apr 2025)