Apache Camel: Camel-PQC Private Key Disclosure via Key Material Written with Default File Permissions
CVSS score
5.5
EPSS probability
—
Risk score
0.6
Published
10 h ago
Etkilenen ürün ve sürüm için yayımlanan güvenlik güncellemesini uygulayın.
Impact on My Inventory
Only the personal products you have added to your account are assessed; an organisation's inventory does not appear here.
Checking session…
Vulnerability description
CVE AI research
DayBreach AI Explanation
Verified against sourcesSources read
1
Source agreement
Tam uyum
Evidence confidence
%55
Short explanation
The CVE-2026-85300 vulnerability in the Apache Camel PQC component causes generated key material to be written to disk using process default umask permissions. On hosts with permissive umasks, this allows private keys to be read by other local accounts.
Possession of the private key defeats every signature and key exchange the deployment performs with it. The exposure affects local parties.
What should be done?
- Upgrade to Apache Camel 4.23.0, 4.18.5, or 4.22.1.
- Place the key directory on a path only the service account can traverse.
- Tighten the process umask and rotate exposed key material.
Chain of evidence and sources
CVE-2026-85300, Apache Camel PQC bileşeninde yanlış varsayılan izinler hatasından kaynaklanmaktadır.
Zafiyet, 4.12.0 ile 4.18.5 ve 4.19.0 ile 4.22.1 arasındaki Apache Camel sürümlerini etkilemektedir.
Anahtar materyali umask izinleriyle diske yazıldığı için yerel hesaplar tarafından okunabilir hale gelmektedir.
Show the technical text from the sources
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 vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CWE: CWE-276
Explanation produced with the local gemini-flash-lite-latest model. Numerical metrics and the KEV, patch and exploit statuses are not determined by AI.
IMPACT: Affected Products and Software
Affected Products
The following products are affected by CVE-2026-85300 vulnerability. Where our threat engine knows the exact affected versions, they are listed below.
| ID | VENDOR | PRODUCT | ACTION |
|---|---|---|---|
| 1 | Apache Software Foundation | Apache Camel | View |
RED HAT CSAF/VEX: Product Impact Check
SCORING: CVSS from Multiple Sources
CVSS Scores
The Common Vulnerability Scoring System is a standardised framework for assessing the severity of vulnerabilities in software and systems. We collect and display CVSS scores from several sources for each CVE.
| SCORE | VERSION | SEVERITY | VECTOR | SOURCE |
|---|---|---|---|---|
| 5.5 | CVSS V31 | MEDIUM | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N | NVD |
| 5.5 | CVSS V3_1 | MEDIUM | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N | CVE CNA |
Patch and Remediation Guide
Solution & Remediation Advisory
6 doğrulanmış yama veya düzeltilmiş sürüm kanıtı bulundu.
Backport to camel-4.22.x, released in 4.22.1 (commit fdb9642e53e47bd0588ab8394db634095e8a19cb)
Open sourceBackport to camel-4.18.x, released in 4.18.5 (commit 2b3e2028491566043955700f639f086c42b9d93a)
Open sourceFix on main, released in 4.23.0 (commit 957b28aa7fad123bfafeea6bfb33a2b1d0a5a188)
Open sourceBackport to camel-4.22.x, released in 4.22.1 (commit fdb9642e53e47bd0588ab8394db634095e8a19cb)
Open sourceBackport to camel-4.18.x, released in 4.18.5 (commit 2b3e2028491566043955700f639f086c42b9d93a)
Open sourcePublic exploit and active exploitation status
Verified exploit intelligence
No verified public PoC, exploit repository or Metasploit module has been found for this CVE yet.
Weakness Classification and Attack Patterns (CWE & CAPEC)
CWE - Common Weakness Enumeration
While CVE identifies specific instances of vulnerabilities, CWE categorises the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-85300 is associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-85300 weaknesses.
Attack Vector and Accessibility
Official Sources and Advisories
CVSS Vector Radar Chart
5.5 / 10Vulnerability Scoring Details
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NYama doğrulandı
Weakness Type (CWE & CAPEC)
Similar Vulnerabilities
Get this vulnerability through the API
Affected products, version ranges, exploitation status and patch information in a single request, with a free key.
curl -H "x-api-key: $DAYBREACH_API_KEY" \ "https://api.daybreach.dev/api/v1/intel/cves/CVE-2026-85300"