{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-92358 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-92358 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-92358 is a medium-severity authentication bypass vulnerability in Red Hat Build of Keycloak, published on 16 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-92358 and fix it if it is affected.\n\nWhat it is: CVE-2026-92358 is a medium-severity authentication bypass vulnerability in Red Hat Build of Keycloak, published on 16 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-92358 in the wild and no public exploit code.\n\nAffected product: Red Hat Build of Keycloak. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-92358/ (Markdown: https://insights.sbomify.com/CVE-2026-92358/index.md)","id":"CVE-2026-92358","markdown":"https://insights.sbomify.com/CVE-2026-92358/index.md","name":"CVE-2026-92358","record":{"aliases":["GHSA-prm3-wvj6-64vx"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Identity and Access Management","requires_auth":"low_privilege","summary":"Attackers can silently re-link accounts using residual proofs, gaining unauthorized access to victim accounts without confirmation.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":6.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-613","name":"DEPRECATED: Insufficient Session Expiration"}],"description":"A flaw was found in the first broker login flow of Keycloak. When a user confirms an account-linking request from a different browser, a temporary proof is created to validate the link. However, this proof is not properly cleared after the link is established or when the user later manually removes the link. An attacker who controls the external identity can exploit this leftover proof to silently re-establish the link and gain unauthorized access to the victims account without any further confirmation.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Keycloak-services: keycloak-services: residual cross-browser account-link proof allows silent re-linking","id":"CVE-2026-92358","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"ag-ui-protocol ag-ui CORSMiddleware utils.py create_strands_app cross-domain policy","id":"CVE-2026-92359"},"packages":[],"prev":{"headline":"a2ui-project a2ui Model Processor model-processor.ts information disclosure","id":"CVE-2026-92357"},"products":["Red Hat Build of Keycloak","Red Hat Single Sign-On 7"],"published":"2026-09-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"total"},"state":"PUBLISHED","updated":"2026-09-17","vendors":["Red Hat"]},"summary":"Attackers can silently re-link accounts using residual proofs, gaining unauthorized access to victim accounts without confirmation.","url":"https://insights.sbomify.com/CVE-2026-92358/"}