This is an automated email from the ASF dual-hosted git repository. oscerd pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/camel-website.git
commit f44b3a1eaefd04cf7b8edbd19693f5d6c693bf42 Author: Andrea Cosentino <[email protected]> AuthorDate: Fri Sep 4 09:09:42 2026 +0200 Added CVE-2026-85260 Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> Claude-Session: https://claude.ai/code/session_013qz9ir11vuQYfQApzwHAHD Signed-off-by: Andrea Cosentino <[email protected]> --- content/security/CVE-2026-85260.md | 21 ++++++++++++++++++++ content/security/CVE-2026-85260.txt.asc | 35 +++++++++++++++++++++++++++++++++ 2 files changed, 56 insertions(+) diff --git a/content/security/CVE-2026-85260.md b/content/security/CVE-2026-85260.md new file mode 100644 index 00000000..63a0d43f --- /dev/null +++ b/content/security/CVE-2026-85260.md @@ -0,0 +1,21 @@ +--- +title: "Apache Camel Security Advisory - CVE-2026-85260" +date: 2026-08-31T10:00:00+02:00 +url: /security/CVE-2026-85260.html +draft: false +type: security-advisory +cve: CVE-2026-85260 +severity: MEDIUM +summary: "Camel-MLLP: protected health information disclosure - logPhi defaulted to true so HL7 payload content was written to the log out of the box, and two code paths logged it regardless of the setting" +description: "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 re [...] +mitigation: "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 upgradin [...] +credit: "This issue was discovered by Claude Security Scan Tool" +affected: "From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1." +fixed: 4.18.5, 4.22.1 and 4.23.0 +--- + +The JIRA ticket: https://issues.apache.org/jira/browse/CAMEL-24454 refers to the various commits that resolved the issue, and has more details. + +The fix was merged on main in https://github.com/apache/camel/pull/25832 (commit dd2bf57190c12ff7f1e97f121738867a680992ce), backported to camel-4.22.x in https://github.com/apache/camel/pull/25944 (commit 95b4c1500001bc32877df5b8fca0bc7bdd080666) and to camel-4.18.x in https://github.com/apache/camel/pull/25946 (commit 4ec9b37d70b08c478966000fb1bd653abfe410e3). + +The issue is classified as CWE-532 Insertion of Sensitive Information into Log File. The camel-4.14.x line reached end of life before this fix and does not receive it; deployments on 4.14.x should move to 4.18.5 or later. diff --git a/content/security/CVE-2026-85260.txt.asc b/content/security/CVE-2026-85260.txt.asc new file mode 100644 index 00000000..5f2f6d50 --- /dev/null +++ b/content/security/CVE-2026-85260.txt.asc @@ -0,0 +1,35 @@ +-----BEGIN PGP SIGNED MESSAGE----- +Hash: SHA512 + +- --- +title: "Apache Camel Security Advisory - CVE-2026-85260" +date: 2026-08-31T10:00:00+02:00 +url: /security/CVE-2026-85260.html +draft: false +type: security-advisory +cve: CVE-2026-85260 +severity: MEDIUM +summary: "Camel-MLLP: protected health information disclosure - logPhi defaulted to true so HL7 payload content was written to the log out of the box, and two code paths logged it regardless of the setting" +description: "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 re [...] +mitigation: "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 upgradin [...] +credit: "This issue was discovered by Claude Security Scan Tool" +affected: "From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1." +fixed: 4.18.5, 4.22.1 and 4.23.0 +- --- + +The JIRA ticket: https://issues.apache.org/jira/browse/CAMEL-24454 refers to the various commits that resolved the issue, and has more details. + +The fix was merged on main in https://github.com/apache/camel/pull/25832 (commit dd2bf57190c12ff7f1e97f121738867a680992ce), backported to camel-4.22.x in https://github.com/apache/camel/pull/25944 (commit 95b4c1500001bc32877df5b8fca0bc7bdd080666) and to camel-4.18.x in https://github.com/apache/camel/pull/25946 (commit 4ec9b37d70b08c478966000fb1bd653abfe410e3). + +The issue is classified as CWE-532 Insertion of Sensitive Information into Log File. The camel-4.14.x line reached end of life before this fix and does not receive it; deployments on 4.14.x should move to 4.18.5 or later. +-----BEGIN PGP SIGNATURE----- + +iQEzBAEBCgAdFiEEJ2Y0ButtuvUpHyYV406fOAL/QQAFAmqabrYACgkQ406fOAL/ +QQCM6Af+LP8uUhXMbduIPRZ1QrITiw/jyxYpABogeB1bBbJY8HYCBSPjxP+6IeyD +add6lm3WByzOx/alWLtWbBbKu/NB9i9qQC3w1wEVzS7p7lnpA60XLZq4KtrMa/dP +a3Kvh5ggPLoGYguqaZrLTfpMR2zpr8+eDQ6/PADlFjzh60wogB84jDDX2i2etKpA +692xTaywnXNaII1OTmALZS3lDPzo+pnm8/sTz6Go+jA4dbizardQZ5VborfGwgdN +Ix+TtnJG2rR84fGaahBNdzyJeHZ39o/T/fa3KtSaF1N//6e1cEf2XEaJYx/YgSkf +z5o5tv3Nfu1Bzkp9Ql0zGoWRWFzChQ== +=+XeZ +-----END PGP SIGNATURE-----
