# Apache Camel: KeycloakSecurityPolicy does not validate issuer of JWT tokens against configured realm

Advisory record · `GHSA-c3f3-cc42-xr9v`

- **Identifiers:** `GHSA-c3f3-cc42-xr9v` · `CVE-2026-23552`
- **State:** Confirmed
- **Severity:** CVSS 9.1 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-346](https://cwe.mitre.org/data/definitions/346.html)
- **Tags:** [CWE-346](https://agentprime.io/advisories/tag/cwe-346.md)
- **Published:** 23 Feb 2026
- **Updated:** 25 Feb 2026
- **Reviewed by a person:** No

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

## Critical

Critical, because:

- CVSS score 9.1: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `org.apache.camel:camel-keycloak` (Maven): affected `>=4.15.0, <4.18.0`; fixed in `4.18.0`

## 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.15.0 before 4.18.0, does not check the issuer claim of JWT tokens against the configured Keycloak realm in KeycloakSecurityPolicy. An attacker holding a valid token from a different realm may have it accepted, which breaks tenant isolation. Upgrade to camel-keycloak 4.18.0 or later.

Written 3 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

- 9.1 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.0061, the 49th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:21 UTC: First seen by agentprime
- 31 Oct 2026, 14:21 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-c3f3-cc42-xr9v)

## Sources

- [GitHub Advisory Database: GHSA-c3f3-cc42-xr9v](https://github.com/advisories/GHSA-c3f3-cc42-xr9v)
- [OSV: GHSA-c3f3-cc42-xr9v](https://osv.dev/vulnerability/GHSA-c3f3-cc42-xr9v)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-23552>
- <https://github.com/apache/camel/commit/c1ed776e3a4fa23d15acf4b9a48fdf758d4316ff>
- <https://camel.apache.org/security/CVE-2026-23552.html>
- <https://github.com/apache/camel>
- <https://github.com/oscerd/CVE-2026-23552>
- <https://issues.apache.org/jira/browse/CAMEL-22854>
- <http://www.openwall.com/lists/oss-security/2026/02/18/7>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-c3f3-cc42-xr9v>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-c3f3-cc42-xr9v/>. Everything for agents: <https://agentprime.io/llms.txt>.