CVE-2026-85300: CWE-276 Incorrect Default Permissions in Apache Software Foundation Apache Camel
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.
CVSS v3.1
Score 5.5medium
Affected software
Apache Software Foundation
Apache Camel
pkg:maven/Apache Software Foundation/org.apache.camel:camel-pqcRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Apache Camel versions >=4.12.0 <4.18.5 and >=4.19.0 <4.22.1 have a CWE-276 Incorrect Default Permissions vulnerability in the PQC component. When writing generated private key material to disk, the component used the process default umask permissions rather than restricting files to owner-only access. On systems with permissive umask settings allowing group or world read access, private keys could be read by other local users. This local exposure can lead to complete compromise of cryptographic operations relying on those keys. The issue is fixed in Apache Camel 4.18.5, 4.22.1, and 4.23.0 by enforcing owner-only permissions on key files. Users unable to upgrade immediately should restrict directory traversal and tighten umask. Any keys written with permissive permissions should be considered compromised and rotated.
Potential Impact
The vulnerability allows local users on the host to read private key material if the system umask permits group or world read access. This compromises the confidentiality of private keys, enabling an attacker with local access to defeat all signature and key exchange protections relying on those keys. The impact is limited to local attackers, not remote adversaries, resulting in a medium severity rating. Complete cryptographic compromise occurs if exploited.
Mitigation Recommendations
A fix is available in Apache Camel versions 4.18.5, 4.22.1, and 4.23.0, which enforce owner-only permissions on key material files. Users should upgrade to these versions to remediate the vulnerability. For deployments unable to upgrade immediately, it is recommended to place the key directory on a path accessible only by the service account and to tighten the process umask to restrict file permissions. Any key material previously written with permissive permissions should be treated as exposed and rotated promptly.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- apache
- Date Reserved
- 2026-09-03T16:39:46.231Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6ad5f5a02cdf04f656435554
Added to database: 10/19/2026, 10:49:04 UTC
Last enriched: 10/19/2026, 11:05:05 UTC
Last updated: 10/19/2026, 19:06:47 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.