{"answers":{"affected":"1 open source package ship an affected version, including keycloak. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-18218 in the wild and no public exploit code.","fix":"Upgrade keycloak to 26.7.3 or later.","what":"CVE-2026-18218 is a medium-severity vulnerability in Redhat Build of Keycloak, published on 31 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-18218 and fix it if it is affected.\n\nWhat it is: CVE-2026-18218 is a medium-severity vulnerability in Redhat Build of Keycloak, published on 31 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-18218 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- keycloak (Bitnami): affected all versions; fixed in 26.7.3\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-18218/ (Markdown: https://insights.sbomify.com/CVE-2026-18218/index.md)","id":"CVE-2026-18218","markdown":"https://insights.sbomify.com/CVE-2026-18218/index.md","name":"CVE-2026-18218","record":{"aliases":["BIT-keycloak-2026-18218","CLEANSTART-2026-PI18525","GHSA-vhxw-j6h3-48jm"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Keycloak identity management","requires_auth":"low_privilege","summary":"Attackers can bypass client-specific token revocation policies if a realm-level policy exists, allowing continued access to user information with invalidated tokens.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"build_of_keycloak","vendor":"redhat"}],"cvss":{"score":4.2,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"A flaw was found in the TokenManager component of the Keycloak identity management service. When an administrator attempts to revoke tokens for a specific application (client) using a \"not-before\" policy, the revocation may be silently ignored if the overall security realm already has an older, non-zero revocation policy in place. This issue can allow previously issued tokens to remain valid for refreshing sessions and accessing user information even after an administrator has attempted to invalidate them.\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Keycloak-services: keycloak-services: client not-before revocation ignored when realm not-before is older but nonzero","id":"CVE-2026-18218","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"redhat:build_of_keycloak","products":["redhat:build_of_keycloak"],"type":"security_feature_bypass","year":"2026"},"n_packages":1,"n_references":4,"next":{"headline":"Binutils: binutils: out-of-bounds write in bfd dlx elf backend relocation processing","id":"CVE-2026-18220"},"packages":[{"ecosystem":"Bitnami","fixed":["26.7.3"],"introduced":["0"],"last_affected":[],"package":"keycloak","purl":"pkg:bitnami/keycloak","source":"BIT-keycloak-2026-18218"}],"prev":{"headline":"Auth bypass in Red Hat Build of Keycloak","id":"CVE-2026-18217"},"products":["Red Hat Data Grid 8","Red Hat JBoss Enterprise Application Platform Expansion Pack","Red Hat Single Sign-On 7","Red Hat build of Keycloak 26.6","Red Hat build of Keycloak 26.6.7"],"published":"2026-07-31","related":[{"cvss_score":8.8,"headline":"Keycloak-services: keycloak-services: dcr protocol mapper type-swap policy bypass allows privilege escalation","id":"CVE-2026-15572","kev_date_added":null,"published":"2026-08-05"},{"cvss_score":8.8,"headline":"Keycloak SAML Broken has Authentication Bypass by Primary Weakness","id":"CVE-2026-3047","kev_date_added":null,"published":"2026-03-05"},{"cvss_score":8.1,"headline":"Keycloak-services: keycloak-services: authorization bypass via unnormalized uri matching in pathmatcher","id":"CVE-2026-15573","kev_date_added":null,"published":"2026-08-05"},{"cvss_score":8.1,"headline":"Keycloak-services: keycloak-services: default dcr policy allows role forgery via user property mappers","id":"CVE-2026-16102","kev_date_added":null,"published":"2026-08-05"},{"cvss_score":8.1,"headline":"Org.keycloak/keycloak-quarkus-server: keycloak: unauthorized access via jwt authorization grant with disabled users","id":"CVE-2026-1609","kev_date_added":null,"published":"2026-07-16"},{"cvss_score":8.1,"headline":"Org.keycloak:keycloak-services: keycloak: authentication bypass via jwt algorithm confusion","id":"CVE-2026-11800","kev_date_added":null,"published":"2026-06-25"},{"cvss_score":8.1,"headline":"Keycloak-policy-enforcer: keycloak policy enforcer: authorization bypass via incorrect uri comparison","id":"CVE-2026-9800","kev_date_added":null,"published":"2026-06-25"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-16","vendors":["Red Hat"]},"summary":"Attackers can bypass client-specific token revocation policies if a realm-level policy exists, allowing continued access to user information with invalidated tokens.","url":"https://insights.sbomify.com/CVE-2026-18218/"}