CVE-2026-85260

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.

• CWE-532

• https://camel.apache.org/security/CVE-2026-85260.htmlMitigation, Patch, Vendor Advisory
• https://github.com/apache/camel/pull/25832Issue Tracking, Patch
• https://github.com/apache/camel/pull/25944Issue Tracking, Patch
• https://github.com/apache/camel/pull/25946Issue Tracking, Patch
• https://issues.apache.org/jira/browse/CAMEL-24454Issue Tracking, Patch, Vendor Advisory

Published

Oct 19, 2026

Last Modified

Nov 3, 2026

Status

Analyzed

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-8525Heap buffer overflow in ANGLE in Google Chrome on Mac prior …8.3
• CVE-2026-85250Improper Restriction of XML External Entity Reference vulner…7.5
• CVE-2026-85251Exposure of Sensitive Information to an Unauthorized Actor v…7.5
• CVE-2026-85254Improper Handling of Case Sensitivity vulnerability in Apach…6.5
• CVE-2026-85257Generation of Error Message Containing Sensitive Information…5.3
• CVE-2026-8526Out of bounds write in WebRTC in Google Chrome prior to 148.…8.8
• CVE-2026-85267A Cross-Site WebSocket Hijacking vulnerability in Cloud Shel…8.7
• CVE-2026-85268A Cross-Site Scripting (XSS) (CWE-79) vulnerability in the a…8.7
• CVE-2026-8527Insufficient validation of untrusted input in Downloads in G…8.8
• CVE-2026-85271Open edX Platform enables the authoring and delivery of onli…6.1
• CVE-2026-85272Open edX Platform enables the authoring and delivery of onli…4.3
• CVE-2026-85274InvoicePlane is a self-hosted open source application for ma…6.5