This is an automated email from the ASF dual-hosted git repository. oscerd pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/camel-website.git
commit f6196fb9acc4b3ff4c67fafec0b5beb6a4e056f8 Author: Andrea Cosentino <[email protected]> AuthorDate: Mon Jun 15 12:27:06 2026 +0200 Added CVE-2026-46455 Signed-off-by: Andrea Cosentino <[email protected]> --- content/security/CVE-2026-46455.md | 17 +++++++++++++++++ content/security/CVE-2026-46455.txt.asc | 31 +++++++++++++++++++++++++++++++ 2 files changed, 48 insertions(+) diff --git a/content/security/CVE-2026-46455.md b/content/security/CVE-2026-46455.md new file mode 100644 index 00000000..87624d68 --- /dev/null +++ b/content/security/CVE-2026-46455.md @@ -0,0 +1,17 @@ +--- +title: "Apache Camel Security Advisory - CVE-2026-46455" +date: 2026-06-09T10:00:00+02:00 +url: /security/CVE-2026-46455.html +draft: false +type: security-advisory +cve: CVE-2026-46455 +severity: MEDIUM +summary: "Apache Camel: Camel-Keycloak: The access-token validity window is not verified because the IS_ACTIVE check is missing from the TokenVerifier, allowing expired tokens to be accepted" +description: "The camel-keycloak security helper KeycloakSecurityHelper.parseAndVerifyAccessToken builds a Keycloak TokenVerifier using withChecks(...) with only the subject-exists check and the realm-URL (issuer) check. Keycloak's TokenVerifier.withChecks(...) appends to an initially empty check list - the upstream default checks are installed only when withDefaultChecks() is called - so the built-in IS_ACTIVE predicate, which validates the token's exp (expiration) and nbf (not-before) [...] +mitigation: "Users are recommended to upgrade to version 4.21.0, which fixes the issue. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. The fix makes KeycloakSecurityHelper.parseAndVerifyAccessToken include the TokenVerifier.IS_ACTIVE check so that expired or not-yet-valid access tokens are rejected, aligning the helper with Keycloak's default check set. For deployments that cannot upgrade immediately, enforce token expiration outside the helper [...] +credit: "This issue was discovered by Andrea Cosentino from Apache Software Foundation and Yu Bao from Paypal" +affected: "From 4.18.0 before 4.18.3, from 4.19.0 before 4.21.0." +fixed: 4.18.3 and 4.21.0 +--- + +The JIRA ticket: https://issues.apache.org/jira/browse/CAMEL-23504 refers to the various commits that resolved the issue, and have more details. The fix was merged on main in https://github.com/apache/camel/pull/23197 (commit 39133b1ada37c60dea53f3b7db720dbd2ae73fa6) and backported to camel-4.18.x (commit 7f4c4736021aff4fad925eca3bf456b95db038f3, PR #23204). The fix adds TokenVerifier.IS_ACTIVE to the withChecks(...) invocation so the token's validity window (exp/nbf) is enforced alongsi [...] diff --git a/content/security/CVE-2026-46455.txt.asc b/content/security/CVE-2026-46455.txt.asc new file mode 100644 index 00000000..1fd1ebea --- /dev/null +++ b/content/security/CVE-2026-46455.txt.asc @@ -0,0 +1,31 @@ +-----BEGIN PGP SIGNED MESSAGE----- +Hash: SHA512 + +- --- +title: "Apache Camel Security Advisory - CVE-2026-46455" +date: 2026-06-09T10:00:00+02:00 +url: /security/CVE-2026-46455.html +draft: false +type: security-advisory +cve: CVE-2026-46455 +severity: MEDIUM +summary: "Apache Camel: Camel-Keycloak: The access-token validity window is not verified because the IS_ACTIVE check is missing from the TokenVerifier, allowing expired tokens to be accepted" +description: "The camel-keycloak security helper KeycloakSecurityHelper.parseAndVerifyAccessToken builds a Keycloak TokenVerifier using withChecks(...) with only the subject-exists check and the realm-URL (issuer) check. Keycloak's TokenVerifier.withChecks(...) appends to an initially empty check list - the upstream default checks are installed only when withDefaultChecks() is called - so the built-in IS_ACTIVE predicate, which validates the token's exp (expiration) and nbf (not-before) [...] +mitigation: "Users are recommended to upgrade to version 4.21.0, which fixes the issue. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. The fix makes KeycloakSecurityHelper.parseAndVerifyAccessToken include the TokenVerifier.IS_ACTIVE check so that expired or not-yet-valid access tokens are rejected, aligning the helper with Keycloak's default check set. For deployments that cannot upgrade immediately, enforce token expiration outside the helper [...] +credit: "This issue was discovered by Andrea Cosentino from Apache Software Foundation and Yu Bao from Paypal" +affected: "From 4.18.0 before 4.18.3, from 4.19.0 before 4.21.0." +fixed: 4.18.3 and 4.21.0 +- --- + +The JIRA ticket: https://issues.apache.org/jira/browse/CAMEL-23504 refers to the various commits that resolved the issue, and have more details. The fix was merged on main in https://github.com/apache/camel/pull/23197 (commit 39133b1ada37c60dea53f3b7db720dbd2ae73fa6) and backported to camel-4.18.x (commit 7f4c4736021aff4fad925eca3bf456b95db038f3, PR #23204). The fix adds TokenVerifier.IS_ACTIVE to the withChecks(...) invocation so the token's validity window (exp/nbf) is enforced alongsi [...] +-----BEGIN PGP SIGNATURE----- + +iQEzBAEBCgAdFiEEJ2Y0ButtuvUpHyYV406fOAL/QQAFAmovy8EACgkQ406fOAL/ +QQDKjQf/eWUv1jZGzXHjjyMgnq+rzZNRYr24rzJfNrYKRJqRlCnAz+j8DZvZk2zc +8U6L23FX6HlSaHtuHCR+/EneCOkV5xaLmELY0Wh20ixHdvvjLBkzbcEuX4odWmwO +2vVOvqZVQK4zluYvefygMh98m2lBYA8sSU+ATNZWOHJqibZF6F+i0qKtVUYVtPOh +NPS1j6NtsXsur7N79XQSkRfZIvJh+0I0+GyAh9GvyT0lZBi7wE7aOdtDscLMkcea +rbSb1SQ+BT0HOkbQuBPtqdJsrnwhDWxFPCeaHrFM3vyXG0fDhUqBqzz42ugPbg10 +KmQYoF9RVPeRsbiwvwXw5k2Tn19pBg== +=eZ3j +-----END PGP SIGNATURE-----
