Live › vulnerability › CVE-2026-85301
Go to dashboardThe 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 written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Applications using Apache Camel 4.15.0 up to but not including 4.18.5, or 4.19.0 up to but not including 4.22.1, that authenticate callers through the Keycloak component's token introspection. Exposure needs an introspection endpoint that omits the iss claim and accepts tokens from more than one issuer, which the sources say is not the default Keycloak arrangement. Teams on other Camel versions, or not using the Keycloak component, can skip it.
No product ranges from the sources yet.
pom.xml or build.gradle) against the fixed releases listed in Fix.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.4.23.0.4.18.5.4.22.1.iss claim and serves exactly one issuer.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-85301")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.