CVE-2026-85301: Apache Camel: Camel-Keycloak Issuer Validation Bypass When the Introspection Response Omits the iss Claim
Improper Authentication vulnerability in Apache Camel Keycloak component.
This issue affects Apache Camel: from 4.15.0 before 4.18.5, from 4.19.0 before 4.22.1.
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 not the default Keycloak arrangement, hence the low severity; where that arrangement exists the consequence is that the deployment authenticates a caller it should have rejected.
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Apache Camelto a version that resolves this vulnerability.Fixed in 4.23.0 - Upgrade
Upgrade
Apache Camelto a version that resolves this vulnerability.Fixed in 4.18.5 - Upgrade
Upgrade
Apache Camelto a version that resolves this vulnerability.Fixed in 4.22.1 - Configuration
For deployments that cannot upgrade immediately, configure the introspection endpoint to return the iss claim and serve exactly one issuer.
Apache Camel Keycloak introspection endpoint iss claim and issuer count = iss present; exactly one issuer
Event History
Frequently Asked Questions
Which deployments are realistically exposed?
Exposure requires an introspection endpoint that both omits the iss claim in its responses and accepts tokens from more than one issuer. This is not the default Keycloak arrangement.
What does an attacker need to exploit this issue?
The attacker needs a token that was not minted by the configured issuer, but is accepted by the configured introspection endpoint. Exploitation also depends on that endpoint returning an introspection response without an iss claim.
How can I determine whether my deployment is affected?
Check whether the configured introspection endpoint returns an iss claim for introspected tokens. Also determine whether it accepts tokens from multiple issuers; both conditions are needed for exposure.
What should be done if an upgrade cannot be applied immediately?
Ensure that the introspection endpoint returns an iss claim, so issuer validation is not skipped. The fixed behavior treats an absent iss claim as a validation failure.
Which releases contain the fix?
Upgrade to Apache Camel 4.23.0. For the LTS release streams, upgrade 4.18.x to 4.18.5 or 4.22.x to 4.22.1.