---
id: "CVE-2026-85301"
kind: "vulnerability"
aliases: ["CVE-2026-85301"]
title: "Apache Camel Keycloak: missing issuer claim skips token validation"
severity: "medium"
cvss: 4.8
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["apache-camel", "java", "keycloak", "package"]
not_affected_if: ["default-config", "not-using-keycloak-component", "single-issuer-with-iss-claim"]
published_at: "2026-10-19T11:17:24+00:00"
first_seen_at: "2026-10-23T21:57:18+00:00"
updated_at: "2026-10-25T04:33:33+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-85301", "first_seen_at": "2026-10-23T21:57:18+00:00"}]
---

# Apache Camel Keycloak: missing issuer claim skips token validation

The Keycloak component in Apache Camel skipped issuer validation of introspected tokens when the introspection response had no iss claim. A token minted by an issuer the deployment does not trust could then be accepted as valid.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the Apache Camel version in the project build file (for example `pom.xml` or `build.gradle`) against the fixed releases listed in Fix.
- Look for the Camel Keycloak component (`camel-keycloak`) in the dependency tree, and check whether the introspection endpoint can return responses without an `iss` claim or can serve tokens from more than one issuer.

## Fix

- Upgrade Apache Camel to `4.23.0`.
- On the 4.18.x LTS stream, upgrade to `4.18.5`.
- On the 4.22.x LTS stream, upgrade to `4.22.1`.
- Until upgraded, ensure the introspection endpoint returns the `iss` claim and serves exactly one issuer.

## Timeline

- 2026-10-23T21:57:18+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-85301

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_