CVE-2026-53913 is an improper authentication / fail-open flaw in the Apache Camel Keycloak component (camel-keycloak). In KeycloakSecurityPolicy, route protection is enforced through KeycloakSecurityProcessor.beforeProcess(), which first checks only for the presence of an access token, then performs role validation only if requiredRoles is non-empty, and permission validation only if requiredPermissions is non-empty. Cryptographic bearer-token verification is performed exclusively inside those role and permission validation paths. Because the documented default/basic setup leaves both requiredRoles and requiredPermissions empty, those checks are skipped and token verification never occurs. In that configuration, any non-null Authorization: Bearer value—including an arbitrary string or a forged/unsigned JWT—is accepted, with no signature, issuer, expiry, or introspection validation, and the request is allowed to reach the protected route. The issue affects Apache Camel versions 4.15.0 before 4.18.3 and 4.19.0 before 4.21.0.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
8 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.