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

Official 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.

Affected products (as reported)

References

• Apache Camel Security Advisory - CVE-2026-85300 vendor-advisory
• CAMEL-24447 issue-tracking
• Fix on main, released in 4.23.0 (commit 957b28aa7fad123bfafeea6bfb33a2b1d0a5a188) patch
• Backport to camel-4.22.x, released in 4.22.1 (commit fdb9642e53e47bd0588ab8394db634095e8a19cb) patch
• Backport to camel-4.18.x, released in 4.18.5 (commit 2b3e2028491566043955700f639f086c42b9d93a) patch