Incorrect Default Permissions Affecting org.apache.camel:camel-pqc package, versions [4.12.0,4.18.5)[4.19.0,4.22.1)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-JAVA-ORGAPACHECAMEL-21430132
- published22 Oct 2026
- disclosed19 Oct 2026
- creditClaude Security
Introduced: 19 Oct 2026
NewCVE-2026-85300 (opens in a new tab)How to fix?
Upgrade org.apache.camel:camel-pqc to version 4.18.5, 4.22.1 or higher.
Overview
Affected versions of this package are vulnerable to Incorrect Default Permissions via the FileBasedKeyLifecycleManager in the PQC component. When it stores generated key material, a process umask that permits group or world access leaves the directory and unencrypted private-key JSON file readable by other local accounts. A local account that reads the key can forge signatures or compromise key exchanges performed with it.
Workarounds
- Place the key directory on a path only the Camel service account can traverse, preventing other local accounts from reading the private keys.
- Tighten the Camel process umask so newly written key material is not readable by group or other users.
- Treat key material already written with permissive permissions as exposed and rotate it, preventing continued use of potentially compromised keys.