PoC Monitor
← All CVEs
CVE-2026-53913published 6 Jul 2026 08:12 UTCData: JSON · API

Apache Software Foundation Apache Camel Keycloak

Apache Camel Keycloak: KeycloakSecurityPolicy verifies the bearer access token only inside its role and permission checks, so in the default configuration the token is never verified and any non-null bearer value is accepted

Improper Authentication, Missing Authentication for Critical Function, Not Failing Securely ('Failing Open') vulnerability in Apache Camel Keycloak Component. The KeycloakSecurityPolicy of camel-keycloak guards a route by running KeycloakSecurityProcessor.beforeProcess(), which performs three checks in sequence: it rejects a request that carries no access token, then - only if requiredRoles is non-empty - validates the roles, and - only if requiredPermissions is non-empty - validates the permissions. The actual cryptographic verification of the bearer access token (signature, issuer and expiry for a local JWT, or active-state and issuer for token introspection) is performed exclusively inside those role and permission checks. KeycloakSecurityPolicy defaults requiredRoles and requiredPermissions to empty - which is the documented 'Basic Setup' - so on a route configured that way the role and permission checks are skipped and the access token is therefore never verified. The token-presence check still rejects a missing token, but an invalid token is accepted: any non-null value in the Authorization: Bearer header - including an arbitrary string or a forged, unsigned JWT - passes the policy and the request reaches the protected route, with no signature, issuer or expiry check and no request to Keycloak. The token is read from the inbound request header because allowTokenFromHeader defaults to true. Because the normal reason to place a route behind this policy is that the route performs server-side work, the bypass results in unauthenticated access to that work; where the protected route forwards to a code-execution-capable producer, it can result in unauthenticated remote code execution. This defect is independent of CVE-2026-23552: that issue concerned the issuer claim and was fixed by adding a check inside the verification routine, but here the verification routine is not reached at all in the default configuration, so the defect remains. This issue affects Apache Camel: from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. Users are recommended to upgrade to version 4.21.0, which fixes the issue. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. For deployments that cannot upgrade immediately, configure a non-empty requiredRoles or requiredPermissions on every KeycloakSecurityPolicy so that the token-verification path is exercised, set allowTokenFromHeader to false where the token is not expected from the request header, or perform token verification at the framework layer ahead of the policy.

First public PoC 15 daysafter publication · 21 Jul 2026
Public PoCs11 on GitHub
CVSS9.8critical · scored by CISA ADP · CWE-287
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Apache Software Foundation Apache Camel Keycloak
  • >= 4.15.0, < 4.18.3
  • >= 4.19.0, < 4.21.0

Fixed in 4.18.3, 4.21.0

Mitigation

Upgrade Apache Camel Keycloak to 4.18.3 or 4.21.0 or later.

References

Timeline

Days relative to CVE publication
-3t=0+3+6+9+12+15CVE published6 Jul 2026 · t = 0First public PoC21 Jul 2026 · t+15d

First public PoC 15 days after publication; not in CISA KEV. First PoC: oscerd/CVE-2026-53913 (created 21 Jul 2026, found by us: backfilled).

PoC repositories

Found on GitHub.

1 PoCs

PoCs 1
RepositoryCreatedStarsAssessment
oscerd/CVE-2026-53913 21 Jul 2026 +15 d 1 PoC

Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.

PoC characteristics

What to hunt for in your logs · from 1 PoC repo

Regex

Generated from PoC characteristics; not yet reviewed. Matches the request path and query.

GET /exploit/attack
(?i)^/exploit/attack(?:[?#].*)?$

Suricata

Template generated from PoC characteristics. Review before deploying.

GET /exploit/attack
alert http any any -> $HOME_NET [8080] (msg:"GG PoC-Monitor CVE-2026-53913 Apache Software Foundation Apache Camel Keycloak exploit attempt"; flow:established,to_server; http.method; content:"GET"; http.uri; content:"/exploit/attack"; reference:url,poc.griffinguard.io/cve/CVE-2026-53913; classtype:web-application-attack; sid:9352611; rev:1;)

Sigma

Template generated from PoC characteristics. Review before deploying.

GET /exploit/attack
title: Apache Software Foundation Apache Camel Keycloak exploit attempt (CVE-2026-53913)
id: gg-pocmon-cve-2026-53913-9352611
status: experimental
description: Request pattern taken from public PoCs for CVE-2026-53913. Generated, not reviewed.
references:
  - https://poc.griffinguard.io/cve/CVE-2026-53913
logsource:
  category: webserver
detection:
  selection:
    cs-method: GET
    cs-uri-stem|contains|all:
      - '/exploit/attack'
  condition: selection
falsepositives:
  - Authorized vulnerability scanning
level: critical
tags:
  - attack.initial_access
  - attack.t1190
  - cve.2026.53913