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 715ea9da6f4dcad6a2d7319ec222b76f1e116b5c
Author: Andrea Cosentino <[email protected]>
AuthorDate: Fri Sep 4 09:09:42 2026 +0200

    Added CVE-2026-85301
    
    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-85301.md      | 21 ++++++++++++++++++++
 content/security/CVE-2026-85301.txt.asc | 35 +++++++++++++++++++++++++++++++++
 2 files changed, 56 insertions(+)

diff --git a/content/security/CVE-2026-85301.md 
b/content/security/CVE-2026-85301.md
new file mode 100644
index 00000000..6f6382fd
--- /dev/null
+++ b/content/security/CVE-2026-85301.md
@@ -0,0 +1,21 @@
+---
+title: "Apache Camel Security Advisory - CVE-2026-85301"
+date: 2026-08-31T10:00:00+02:00
+url: /security/CVE-2026-85301.html
+draft: false
+type: security-advisory
+cve: CVE-2026-85301
+severity: MEDIUM
+summary: "Camel-Keycloak: issuer validation bypass - the issuer check was 
skipped rather than failed when the token introspection response carried no iss 
claim, so a token from an unintended issuer could be accepted"
+description: "The security processor validated the issuer of an introspected 
token only when the introspection response actually carried an iss claim. When 
the claim was absent the check was skipped rather than treated as a failure, so 
a token that the configured issuer did not mint could be accepted provided the 
introspection endpoint answered without naming an issuer. Reaching this 
requires an introspection endpoint that omits iss and accepts tokens from more 
than one issuer, which is  [...]
+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. An absent iss claim is now 
treated as a validation failure rather than as a reason to skip the check. For 
deployments that cannot upgrade immediately, ensure the introspection endpoint 
returns the iss claim, and that it serves exactly one issuer."
+credit: "This issue was discovered by Claude Security Scan Tool"
+affected: "From 4.15.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-24448 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/25827 
(commit ee074873e92dde749aa183d26205b92ddc9bde2a), backported to camel-4.22.x 
in https://github.com/apache/camel/pull/25858 (commit 
c9e69aae7b374cc38d28c1c8dca744c1ba4d6718) and to camel-4.18.x in 
https://github.com/apache/camel/pull/25859 (commit 
aba0f7551e4f63e1f37498454870a49ccdaae727).
+
+The issue is classified as CWE-287 Improper Authentication. 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-85301.txt.asc 
b/content/security/CVE-2026-85301.txt.asc
new file mode 100644
index 00000000..db50bc48
--- /dev/null
+++ b/content/security/CVE-2026-85301.txt.asc
@@ -0,0 +1,35 @@
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA512
+
+- ---
+title: "Apache Camel Security Advisory - CVE-2026-85301"
+date: 2026-08-31T10:00:00+02:00
+url: /security/CVE-2026-85301.html
+draft: false
+type: security-advisory
+cve: CVE-2026-85301
+severity: MEDIUM
+summary: "Camel-Keycloak: issuer validation bypass - the issuer check was 
skipped rather than failed when the token introspection response carried no iss 
claim, so a token from an unintended issuer could be accepted"
+description: "The security processor validated the issuer of an introspected 
token only when the introspection response actually carried an iss claim. When 
the claim was absent the check was skipped rather than treated as a failure, so 
a token that the configured issuer did not mint could be accepted provided the 
introspection endpoint answered without naming an issuer. Reaching this 
requires an introspection endpoint that omits iss and accepts tokens from more 
than one issuer, which is  [...]
+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. An absent iss claim is now 
treated as a validation failure rather than as a reason to skip the check. For 
deployments that cannot upgrade immediately, ensure the introspection endpoint 
returns the iss claim, and that it serves exactly one issuer."
+credit: "This issue was discovered by Claude Security Scan Tool"
+affected: "From 4.15.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-24448 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/25827 
(commit ee074873e92dde749aa183d26205b92ddc9bde2a), backported to camel-4.22.x 
in https://github.com/apache/camel/pull/25858 (commit 
c9e69aae7b374cc38d28c1c8dca744c1ba4d6718) and to camel-4.18.x in 
https://github.com/apache/camel/pull/25859 (commit 
aba0f7551e4f63e1f37498454870a49ccdaae727).
+
+The issue is classified as CWE-287 Improper Authentication. 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/
+QQChgAf/fYxflNpfwa45u1/87er8qpKjWInE/veG81Ux9Bj0QGRh0B3zuGs4M9xb
+NEzJG+ZoXAg0WCM11WbXqReQ+P+4OojKhADXIc3dk+zgp7lv9L3wLAjkoelqzRQ+
+Si1gdaLhhC1Spai44BjyXrtNJJ5LNOiagWBHASqq4G2fX2aC9u+dTo8fRqd0LWh7
+OoVbYQga1RJ4JEYw7t1tm9QLt1bxJ9FhvseraOO5GxwdUlYW3pp/ppMXug54Y7ut
+LbTYpsz0wRq291D+luSZD+kUvOTiBr7zi5FfueOYWM+h8Z0bfgO+AKJFD6iFvVKf
+svNxJ1iLFpxIG2JsEinqm8zG46qGKw==
+=ycjk
+-----END PGP SIGNATURE-----

Reply via email to