{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-85260 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-85260 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-85260 is a medium-severity vulnerability in Apache Camel, published on 19 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-85260 and fix it if it is affected.\n\nWhat it is: CVE-2026-85260 is a medium-severity vulnerability in Apache Camel, published on 19 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-85260 in the wild and no public exploit code.\n\nAffected product: Apache Camel. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-85260/ (Markdown: https://insights.sbomify.com/CVE-2026-85260/index.md)","id":"CVE-2026-85260","markdown":"https://insights.sbomify.com/CVE-2026-85260/index.md","name":"CVE-2026-85260","record":{"aliases":["GHSA-9gc9-j9wv-mmw8"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Apache Camel MLLP","requires_auth":"low_privilege","summary":"Apache Camel MLLP component logs protected health information by default, exposing patient data to application logs unless explicitly disabled or patched.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"Insertion of Sensitive Information into Log File vulnerability in Apache Camel MLLP component.\n\nThis issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.\n\nThe 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.\n\nUpgrade 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-10-20","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-10-20T08:20:58Z","kind":"github_poc","ref":"https://github.com/oscerd/CVE-2026-85260","stars":0,"title":"Reproducer for CVE-2026-85260 — Apache Camel camel-mllp protected health information logging (CWE-532); Spring Boot + Quarkus, affected vs fixed"}],"tier":"poc_unverified"},"has_fix":false,"headline":"Apache Camel: Camel-MLLP Protected Health Information Disclosure to Logs by Default","id":"CVE-2026-85260","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Cross-Site WebSocket Hijacking in Google Cloud Shell","id":"CVE-2026-85267"},"packages":[],"prev":{"headline":"Apache Camel: Camel-CXF Information Disclosure via Unmuted Consumer Exceptions","id":"CVE-2026-85257"},"products":["Apache Camel"],"published":"2026-10-19","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Apache Software Foundation"]},"summary":"Apache Camel MLLP component logs protected health information by default, exposing patient data to application logs unless explicitly disabled or patched.","url":"https://insights.sbomify.com/CVE-2026-85260/"}