{"answers":{"affected":"4 open source packages ship an affected version, including org.apache.camel:camel-keycloak. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-53913 in the wild and no public exploit code.","fix":"Upgrade org.apache.camel:camel-keycloak to a fixed version for your release line: 4.18.3 or 4.21.0.","what":"CVE-2026-53913 is a critical authentication bypass vulnerability in Apache Camel, published on 6 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-53913 and fix it if it is affected.\n\nWhat it is: CVE-2026-53913 is a critical authentication bypass vulnerability in Apache Camel, published on 6 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-53913 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.camel:camel-keycloak (Maven): affected from 4.15.0; fixed in 4.18.3\n- org.apache.camel:camel-keycloak (Maven): affected from 4.15.0; fixed in 4.18.3\n- org.apache.camel:camel-keycloak (Maven): affected from 4.19.0; fixed in 4.21.0\n- org.apache.camel:camel-keycloak (Maven): affected from 4.19.0; fixed in 4.21.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-53913/ (Markdown: https://insights.sbomify.com/CVE-2026-53913/index.md)","id":"CVE-2026-53913","markdown":"https://insights.sbomify.com/CVE-2026-53913/index.md","name":"CVE-2026-53913","record":{"aliases":["GHSA-qvc3-6q9x-95pj"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["security_bypass","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache Camel Keycloak","requires_auth":"none","summary":"Attackers can bypass authentication in Apache Camel Keycloak routes by sending any non-null bearer token, potentially leading to unauthenticated remote code execution.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"camel","vendor":"apache"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-636","name":"Not Failing Securely"},{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"},{"id":"CWE-287","name":"Improper Authentication"}],"description":"Improper Authentication, Missing Authentication for Critical Function, Not Failing Securely ('Failing Open') vulnerability in Apache Camel Keycloak Component.\n\nThe 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.\nThis issue affects Apache Camel: from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0.\n\nUsers 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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":"2026-07-21","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-07-21T12:46:27Z","kind":"github_poc","ref":"https://github.com/oscerd/CVE-2026-53913","stars":1,"title":"PoC reproducer for CVE-2026-53913 (Apache Camel camel-keycloak): KeycloakSecurityPolicy fails open in the Basic Setup — with no required roles/permissions the token is never verified, so any forged/garbage bearer token bypasses authentication (unauthenticated RCE). Fixed in 4.18.3/4.21.0."}],"tier":"poc_unverified"},"has_fix":true,"headline":"Apache Camel: KeycloakSecurityPolicy has Improper Authentication, Missing Authentication for Critical Function and Failing Open Vulnerabilities","id":"CVE-2026-53913","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"apache:camel","products":["apache:camel"],"type":"auth_bypass","year":"2026"},"n_packages":4,"n_references":1,"next":{"headline":"JetBrains Kotlin: Unsafe Deserialization in Kotlin Build Cache Enables Code Execution","id":"CVE-2026-53914"},"packages":[{"ecosystem":"Maven","fixed":["4.18.3"],"introduced":["4.15.0"],"last_affected":[],"package":"org.apache.camel:camel-keycloak","purl":null,"source":"GHSA-qvc3-6q9x-95pj"},{"ecosystem":"Maven","fixed":["4.18.3"],"introduced":["4.15.0"],"last_affected":[],"package":"org.apache.camel:camel-keycloak","purl":"pkg:maven/org.apache.camel/camel-keycloak","source":"GHSA-qvc3-6q9x-95pj"},{"ecosystem":"Maven","fixed":["4.21.0"],"introduced":["4.19.0"],"last_affected":[],"package":"org.apache.camel:camel-keycloak","purl":null,"source":"GHSA-qvc3-6q9x-95pj"},{"ecosystem":"Maven","fixed":["4.21.0"],"introduced":["4.19.0"],"last_affected":[],"package":"org.apache.camel:camel-keycloak","purl":"pkg:maven/org.apache.camel/camel-keycloak","source":"GHSA-qvc3-6q9x-95pj"}],"prev":{"headline":"Cerebrate self-registration password hash exposure via inbox and audit log views","id":"CVE-2026-53912"},"products":["Apache Camel Keycloak"],"published":"2026-07-06","related":[{"cvss_score":10,"headline":"Apache camel-coap allows header injection that can lead to remote code execution","id":"CVE-2026-33453","kev_date_added":null,"published":"2026-04-27"},{"cvss_score":9.9,"headline":"Apache Camel has an incomplete fix for CVE-2025-27636","id":"CVE-2026-40453","kev_date_added":null,"published":"2026-04-27"},{"cvss_score":9.8,"headline":"Apache Camel K: Camel K Tenant repositories reach Maven execution inside operator pod","id":"CVE-2026-80351","kev_date_added":null,"published":"2026-09-10"},{"cvss_score":9.8,"headline":"Apache Camel K: Camel K Master trait serviceAccountName YAML injection lets CR author apply arbitrary objects","id":"CVE-2026-80352","kev_date_added":null,"published":"2026-09-10"},{"cvss_score":9.8,"headline":"Apache Camel: Camel-Atmosphere-Websocket: WebSocket dispatch header injection","id":"CVE-2026-71300","kev_date_added":null,"published":"2026-08-24"},{"cvss_score":9.8,"headline":"Apache Camel-Undertow: the endpoint discarded the undertow-specific header filter strategy in favour of the base HTTP one, so the undertow filtering never ran on endpoint-configured routes","id":"CVE-2026-78329","kev_date_added":null,"published":"2026-08-24"},{"cvss_score":9.8,"headline":"Apache Camel-PQC: The AWS Secrets Manager key-lifecycle manager deserializes persisted key metadata with java.io.ObjectInputStream and no ObjectInputFilter","id":"CVE-2026-43867","kev_date_added":null,"published":"2026-07-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-07","vendors":["Apache Software Foundation"]},"summary":"Attackers can bypass authentication in Apache Camel Keycloak routes by sending any non-null bearer token, potentially leading to unauthenticated remote code execution.","url":"https://insights.sbomify.com/CVE-2026-53913/"}