This is an automated email from the ASF dual-hosted git repository. oscerd pushed a commit to branch new-wave-of-cves in repository https://gitbox.apache.org/repos/asf/camel-website.git
commit 3266b124cdab7e08a79b1d675f4a016cacd63c7d Author: Andrea Cosentino <[email protected]> AuthorDate: Fri Sep 4 09:09:42 2026 +0200 Added CVE-2026-85300 Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> Claude-Session: https://claude.ai/code/session_013qz9ir11vuQYfQApzwHAHD Signed-off-by: Andrea Cosentino <[email protected]> --- content/security/CVE-2026-85300.md | 21 ++++++++++++++++++++ content/security/CVE-2026-85300.txt.asc | 35 +++++++++++++++++++++++++++++++++ 2 files changed, 56 insertions(+) diff --git a/content/security/CVE-2026-85300.md b/content/security/CVE-2026-85300.md new file mode 100644 index 00000000..2c00e21a --- /dev/null +++ b/content/security/CVE-2026-85300.md @@ -0,0 +1,21 @@ +--- +title: "Apache Camel Security Advisory - CVE-2026-85300" +date: 2026-08-31T10:00:00+02:00 +url: /security/CVE-2026-85300.html +draft: false +type: security-advisory +cve: CVE-2026-85300 +severity: MEDIUM +summary: "Camel-PQC: private key disclosure - generated key material was written to disk with the process default file permissions rather than restricted to the owner, so any local account able to read the directory could read the private key" +description: "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 wher [...] +mitigation: "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 expo [...] +credit: "This issue was discovered by Claude Security Scan Tool" +affected: "From 4.12.0 before 4.18.5, from 4.19.0 before 4.22.1." +fixed: 4.18.5, 4.22.1 and 4.23.0 +--- + +The JIRA ticket: https://issues.apache.org/jira/browse/CAMEL-24447 refers to the various commits that resolved the issue, and has more details. + +The fix was merged on main in https://github.com/apache/camel/pull/25826 (commit 957b28aa7fad123bfafeea6bfb33a2b1d0a5a188), backported to camel-4.22.x in https://github.com/apache/camel/pull/25856 (commit fdb9642e53e47bd0588ab8394db634095e8a19cb) and to camel-4.18.x in https://github.com/apache/camel/pull/25857 (commit 2b3e2028491566043955700f639f086c42b9d93a). + +The issue is classified as CWE-276 Incorrect Default Permissions. The camel-4.14.x line reached end of life before this fix and does not receive it; deployments on 4.14.x should move to 4.18.5 or later. diff --git a/content/security/CVE-2026-85300.txt.asc b/content/security/CVE-2026-85300.txt.asc new file mode 100644 index 00000000..7126c897 --- /dev/null +++ b/content/security/CVE-2026-85300.txt.asc @@ -0,0 +1,35 @@ +-----BEGIN PGP SIGNED MESSAGE----- +Hash: SHA512 + +- --- +title: "Apache Camel Security Advisory - CVE-2026-85300" +date: 2026-08-31T10:00:00+02:00 +url: /security/CVE-2026-85300.html +draft: false +type: security-advisory +cve: CVE-2026-85300 +severity: MEDIUM +summary: "Camel-PQC: private key disclosure - generated key material was written to disk with the process default file permissions rather than restricted to the owner, so any local account able to read the directory could read the private key" +description: "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 wher [...] +mitigation: "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 expo [...] +credit: "This issue was discovered by Claude Security Scan Tool" +affected: "From 4.12.0 before 4.18.5, from 4.19.0 before 4.22.1." +fixed: 4.18.5, 4.22.1 and 4.23.0 +- --- + +The JIRA ticket: https://issues.apache.org/jira/browse/CAMEL-24447 refers to the various commits that resolved the issue, and has more details. + +The fix was merged on main in https://github.com/apache/camel/pull/25826 (commit 957b28aa7fad123bfafeea6bfb33a2b1d0a5a188), backported to camel-4.22.x in https://github.com/apache/camel/pull/25856 (commit fdb9642e53e47bd0588ab8394db634095e8a19cb) and to camel-4.18.x in https://github.com/apache/camel/pull/25857 (commit 2b3e2028491566043955700f639f086c42b9d93a). + +The issue is classified as CWE-276 Incorrect Default Permissions. The camel-4.14.x line reached end of life before this fix and does not receive it; deployments on 4.14.x should move to 4.18.5 or later. +-----BEGIN PGP SIGNATURE----- + +iQEzBAEBCgAdFiEEJ2Y0ButtuvUpHyYV406fOAL/QQAFAmqabrYACgkQ406fOAL/ +QQBVdQf7BNo5MhHVLF7E4fT/nCWcSB9p41C07A4v0BnKDxdZG39KwKIye9J76YMk +p4+TsJTkJN1uZTPNsNKkYjZT5Zgkob00tPVVVo7j9H26EmojWqBD06y9KJKLxxnu +LjyVSUvOkJmLJm35ctTyqXxx63mkdE+6Ogvhr8ZOXamHadlfUzRcDj1vJiwy1txo +WND41SrE9KlwsIewnWe7iX2JzNjjm9GywLORaB7a+ewVdj5sf+O8xUyhwo2DlDlT +9E5Sox5xyicEonT1YU9fEEQBPsEs3I2EU3R3wX9p481dAZ8AjZu05R6v/h/bdqbu +skpz9akYn/QFNvAYU9B3DELA7HIwww== +=91Jh +-----END PGP SIGNATURE-----
