# CVE-2026-85260: Apache Camel MLLP component insertion of sensitive information into logs

Source: https://junglewise.ai/threats/cve-2026-85260-insertion-of-sensitive-information-into-log-file-vulnerability-in  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-19. Updated: 2026-10-19  
License: CC BY 4.0 with a link back

CVE-2026-85260 · Severity: medium · CVSS 5.5 · Published 2026-10-19

Apache Camel's MLLP component is used to transport HL7 clinical messages containing patient data. A vulnerability causes sensitive patient information to be written to application logs by default, and even when logging is disabled, certain code paths continue to expose this data. Attackers or unauthorized users with access to application logs can read protected health information, creating compliance and privacy violations.

Technologies: [Apache Camel](https://junglewise.ai/threats/technologies/camel). Vendors: [Apache](https://junglewise.ai/threats/vendors/apache).

## Quick answers

**Is CVE-2026-85260 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-85260 being exploited in the wild.

**How severe is CVE-2026-85260?** Medium severity, with a CVSS score of 5.5, published 19 October 2026.

**Which products and versions are affected?** Apache Camel 4.0.0 before 4.18.5, 4.19.0 before 4.22.1.

**Is there a fix for CVE-2026-85260?** Yes: fixed in Apache Camel 4.23.0; 4.18.5 (4.18.x LTS); 4.22.1 (4.22.x LTS). Until then: Set logPhi=false immediately to minimize exposure; be aware that two code paths will continue to log payload content until upgrade, so restrict access to application logs accordingly. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-85260 attacked?** It is attacked with local access, in a software library.

**Am I affected by CVE-2026-85260?** Check whether you run Apache Camel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in Apache Camel 4.23.0; 4.18.5 (4.18.x LTS); 4.22.1 (4.22.x LTS)

Set logPhi=false immediately to minimize exposure; be aware that two code paths will continue to log payload content until upgrade, so restrict access to application logs accordingly.

## Technical details

The camel-mllp component has a logPhi option controlling whether HL7 payload (containing protected health information) is logged; it defaults to true in vulnerable versions, and two additional code paths write payload content regardless of the setting. An attacker with read access to application logs can recover patient data without authentication. The vulnerability is fixed by upgrading to patched versions where the default is changed to false and all paths respect the setting.

## Affected products

- Apache Camel 4.0.0 before 4.18.5, 4.19.0 before 4.22.1

## Timeline

- 2026-10-19: disclosed

## Related threats

- [Apache Camel SSRF in A2A webhook validator](https://junglewise.ai/threats/cve-2026-71569-server-side-request-forgery-ssrf-vulnerability-in-apache-camel)
- [Apache Camel OAuth component cache containing sensitive information](https://junglewise.ai/threats/cve-2026-94386-use-of-cache-containing-sensitive-information-vulnerability-in)
- [Apache Camel Saxon component XXE in XQuery evaluation](https://junglewise.ai/threats/cve-2026-90885-improper-restriction-of-xml-external-entity-reference)
- [Apache Camel AWS2-S3 expression language injection in key handling](https://junglewise.ai/threats/cve-2026-95664-improper-neutralization-of-special-elements-used-in-an-expression)
- [Apache Camel Keycloak security policy token expiration bypass](https://junglewise.ai/threats/cve-2026-95663-insufficient-session-expiration-vulnerability-in-apache-camel)