Severity:
CVSS 3.1: 5.5 (medium) CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Affected versions:
- Apache Camel (org.apache.camel:camel-pqc) 4.12.0 before 4.18.5
- Apache Camel (org.apache.camel:camel-pqc) 4.19.0 before 4.22.1
- Apache Camel (org.apache.camel:camel-pqc) 4.18.5 unaffected
- Apache Camel (org.apache.camel:camel-pqc) 4.22.1 unaffected
- Apache Camel (org.apache.camel:camel-pqc) 4.23.0 unaffected
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.
Solution:
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.
Work Arounds:
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.
Credit:
Claude Security (finder)
Andrea Cosentino (remediation developer)
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
https://camel.apache.org/
https://www.cve.org/CVERecord?id=CVE-2026-85300
