{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-85300 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-85300 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-85300 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-85300 and fix it if it is affected.\n\nWhat it is: CVE-2026-85300 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-85300 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-85300/ (Markdown: https://insights.sbomify.com/CVE-2026-85300/index.md)","id":"CVE-2026-85300","markdown":"https://insights.sbomify.com/CVE-2026-85300/index.md","name":"CVE-2026-85300","record":{"aliases":["GHSA-p6fv-47jx-6w55"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Apache Camel PQC component","requires_auth":"low_privilege","summary":"Local attackers can read private keys if the host umask allows group or world read access to files written by the Apache Camel PQC component.","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-276","name":"Incorrect Default Permissions"}],"description":"Incorrect Default Permissions vulnerability in Apache Camel PQC component.\n\nThis issue affects Apache Camel: from 4.12.0 before 4.18.5, from 4.19.0 before 4.22.1.\n\nWhen the component wrote generated key material to disk it did so with the permissions the process default umask produced, rather than restricting the file to its owner. On a host whose umask allows group or world read, the private key was therefore readable by other local accounts. The exposure is to a local party rather than to the remote sender that the Camel threat model treats as the primary adversary, which is why the severity is assessed low, but the consequence where it applies is complete: possession of the private key defeats every signature and key exchange the deployment performs with it.\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. Key material is now written with owner-only permissions. For deployments that cannot upgrade immediately, place the key directory on a path only the service account can traverse, and tighten the process umask. Key material already written with permissive permissions should be treated as exposed and rotated.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-10-20","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-10-20T09:36:08Z","kind":"github_poc","ref":"https://github.com/oscerd/CVE-2026-85300","stars":0,"title":"Reproducer for CVE-2026-85300 — Apache Camel camel-pqc private key written with permissive file permissions (CWE-276); Spring Boot + Quarkus, affected vs fixed"}],"tier":"poc_unverified"},"has_fix":false,"headline":"Apache Camel: Camel-PQC Private Key Disclosure via Key Material Written with Default File Permissions","id":"CVE-2026-85300","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":"Apache Camel: Camel-Keycloak Issuer Validation Bypass When the Introspection Response Omits the iss Claim","id":"CVE-2026-85301"},"packages":[],"prev":{"headline":"Missing Authorization in Compute Engine allows Cross-Project Disk Exfiltration","id":"CVE-2026-85299"},"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":"Local attackers can read private keys if the host umask allows group or world read access to files written by the Apache Camel PQC component.","url":"https://insights.sbomify.com/CVE-2026-85300/"}