{"answers":{"affected":"2 open source packages ship an affected version, including org.apache.camel:camel-keycloak. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-23552 exists.","fix":"Upgrade org.apache.camel:camel-keycloak to 4.18.0 or later.","what":"CVE-2026-23552 is a critical authentication bypass vulnerability in Apache Camel, published on 23 Feb 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-23552 and fix it if it is affected.\n\nWhat it is: CVE-2026-23552 is a critical authentication bypass vulnerability in Apache Camel, published on 23 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-23552 exists.\n\nAffected packages and fixed versions:\n- org.apache.camel:camel-keycloak (Maven): affected from 4.15.0; fixed in 4.18.0\n- org.apache.camel:camel-keycloak (Maven): affected from 4.15.0; fixed in 4.18.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-23552/ (Markdown: https://insights.sbomify.com/CVE-2026-23552/index.md)","id":"CVE-2026-23552","markdown":"https://insights.sbomify.com/CVE-2026-23552/index.md","name":"CVE-2026-23552","record":{"aliases":["GHSA-c3f3-cc42-xr9v"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache Camel Keycloak","requires_auth":"none","summary":"Attackers can bypass tenant isolation by using tokens from one Keycloak realm to access resources in another due to missing issuer validation.","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.1,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-346","name":"Origin Validation Error"}],"description":"Cross-Realm Token Acceptance Bypass in KeycloakSecurityPolicy Apache Camel Keycloak component. \n\nThe Camel-Keycloak KeycloakSecurityPolicy does not validate the iss (issuer) claim of JWT tokens against the configured realm. A token issued by one Keycloak realm is silently accepted by a policy configured for a completely different realm, breaking tenant isolation.\nThis issue affects Apache Camel: from 4.15.0 before 4.18.0.\n\nUsers are recommended to upgrade to version 4.18.0, which fixes the issue.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":"2026-02-09","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-02-09T12:50:28Z","kind":"github_poc","ref":"https://github.com/oscerd/CVE-2026-23552","stars":0,"title":"CVE-2026-23552 - Cross-Realm Token Acceptance in camel-keycloak"}],"tier":"weaponised"},"has_fix":true,"headline":"Apache Camel: Camel-Keycloak: Cross-Realm Token Acceptance Bypass in KeycloakSecurityPolicy","id":"CVE-2026-23552","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"apache:camel","products":["apache:camel"],"type":"auth_bypass","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"x86: incomplete IBPB for vCPU isolation","id":"CVE-2026-23553"},"packages":[{"ecosystem":"Maven","fixed":["4.18.0"],"introduced":["4.15.0"],"last_affected":[],"package":"org.apache.camel:camel-keycloak","purl":null,"source":"GHSA-c3f3-cc42-xr9v"},{"ecosystem":"Maven","fixed":["4.18.0"],"introduced":["4.15.0"],"last_affected":[],"package":"org.apache.camel:camel-keycloak","purl":"pkg:maven/org.apache.camel/camel-keycloak","source":"GHSA-c3f3-cc42-xr9v"}],"prev":{"headline":"WordPress Modular DS plugin \u003c= 2.5.1 - Privilege Escalation vulnerability","id":"CVE-2026-23550"},"products":["Apache Camel"],"published":"2026-02-23","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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-23","vendors":["Apache Software Foundation"]},"summary":"Attackers can bypass tenant isolation by using tokens from one Keycloak realm to access resources in another due to missing issuer validation.","url":"https://insights.sbomify.com/CVE-2026-23552/"}