Is CVE-2026-53913 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-53913 being exploited in the wild.

How severe is CVE-2026-53913?

Critical severity, with a CVSS score of 9.8, published 6 July 2026.

Which products and versions are affected?

Apache Software Foundation Camel Keycloak 4.15.0 to 4.18.2, 4.19.0 to 4.20.0, 4.15.0 to 4.18.2, 4.19.0 to 4.20.x; org.apache.camel:camel-keycloak (Maven) ECOSYSTEM:introduced=4.15.0,fixed=4.18.3.

Is there a fix for CVE-2026-53913?

Yes. org.apache.camel:camel-keycloak (Maven): upgrade to 4.18.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-53913 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-53913?

Check whether you run Apache Software Foundation Camel Keycloak or org.apache.camel:camel-keycloak (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-53913: Apache Camel Keycloak authentication bypass in KeycloakSecurityPolicy

CVE-2026-53913 · Severity: critical · CVSS 9.8 · Published 2026-07-06

Apache Camel is an integration framework used to connect different software applications. A security flaw in its Keycloak component allows attackers to bypass identity checks by providing any random text instead of a valid security token. This could allow unauthorized individuals to access sensitive internal data or even take control of the server if the system is configured to execute commands based on these requests.

Technologies: org.apache.camel:camel-keycloak (Maven). Vendors: Apache Software Foundation, Maven.

Quick answers

Is CVE-2026-53913 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-53913 being exploited in the wild.
How severe is CVE-2026-53913?: Critical severity, with a CVSS score of 9.8, published 6 July 2026.
Which products and versions are affected?: Apache Software Foundation Camel Keycloak 4.15.0 to 4.18.2, 4.19.0 to 4.20.0, 4.15.0 to 4.18.2, 4.19.0 to 4.20.x; org.apache.camel:camel-keycloak (Maven) ECOSYSTEM:introduced=4.15.0,fixed=4.18.3.
Is there a fix for CVE-2026-53913?: Yes. org.apache.camel:camel-keycloak (Maven): upgrade to 4.18.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-53913 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-53913?: Check whether you run Apache Software Foundation Camel Keycloak or org.apache.camel:camel-keycloak (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

org.apache.camel:camel-keycloak (Maven): upgrade to 4.18.3 or later

# set org.apache.camel:camel-keycloak to 4.18.3 in your pom.xml or build.gradle

Technical details

The KeycloakSecurityPolicy in camel-keycloak fails to perform cryptographic verification of bearer tokens when 'requiredRoles' and 'requiredPermissions' are empty (the default 'Basic Setup'). While the policy checks for the presence of a token, it does not reach the verification routine (signature, issuer, or expiry checks) unless specific roles or permissions are defined. An attacker can provide an arbitrary string or a forged, unsigned JWT in the Authorization header to bypass authentication. If the protected route forwards to a code-execution-capable producer, this can lead to remote code execution. The issue is fixed in versions 4.18.3 and 4.21.0.

Affected products

Apache camel-keycloak 4.15.0 to 4.18.2, 4.19.0 to 4.20.0

Identifiers

CVE-2026-53913
GHSA-qvc3-6q9x-95pj

Timeline

2026-07-06: disclosed
2026-07-06: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.