CVE-2026-85300
Camel-PQC: private key disclosure - generated key material was written to disk with the process default file permissions rather than restricted to the owner, so any local account able to read the directory could read the private key
Description
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.
Mitigation
Credit
This issue was discovered by Claude Security Scan Tool
Notes
The JIRA ticket: https://issues.apache.org/jira/browse/CAMEL-24447 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/25826 (commit 957b28aa7fad123bfafeea6bfb33a2b1d0a5a188), backported to camel-4.22.x in https://github.com/apache/camel/pull/25856 (commit fdb9642e53e47bd0588ab8394db634095e8a19cb) and to camel-4.18.x in https://github.com/apache/camel/pull/25857 (commit 2b3e2028491566043955700f639f086c42b9d93a).
The issue is classified as CWE-276 Incorrect Default Permissions. 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.