Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-mqwc-6qwc-v9gq

Apache 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

CVSS 9.8 CriticalCriticalEPSS 0.0069 · 53rd percentile

Critical, because:

  • CVSS score 9.8: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 6 Jul 2026, 09:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.apache.camel:camel-keycloakMaven>=4.18.0, <4.18.3 || >=4.19.0, <4.21.04.18.3, 4.21.0
Identifiers
GHSA-mqwc-6qwc-v9gq · CVE-2026-46455
Weakness (CWE)
CWE-613
Tags
Published
6 Jul 2026
Updated
28 Aug 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Apache Camel's camel-keycloak component, versions 4.18.0 before 4.18.3 and 4.19.0 before 4.21.0, does not check whether access tokens are expired or not yet valid, so expired tokens are accepted. An attacker holding an expired or not-yet-valid access token can use it to authenticate to routes that rely on this helper. Upgrade to camel-keycloak 4.21.0, or 4.18.3 if on the 4.18.x stream. Until then, validate the token's exp and nbf claims in the route itself.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.8 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.0069, the 53rd percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:19 UTC First seen by agentprime
  2. 31 Oct 2026, 14:19 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.