{"answers":{"affected":"2 open source packages ship an affected version, including org.keycloak:keycloak-parent.","exploited":"There is no known exploitation of CVE-2026-0707 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-0707 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-0707 is a medium-severity vulnerability in Red Hat build of Keycloak 26.4, published on 8 Jan 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-0707 and fix it if it is affected.\n\nWhat it is: CVE-2026-0707 is a medium-severity vulnerability in Red Hat build of Keycloak 26.4, published on 8 Jan 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-0707 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.keycloak:keycloak-parent (Maven): affected all versions up to 26.5.0; no fix listed\n- org.keycloak:keycloak-parent (Maven): affected all versions up to 26.5.0; no fix listed\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-0707/ (Markdown: https://insights.sbomify.com/CVE-2026-0707/index.md)","id":"CVE-2026-0707","markdown":"https://insights.sbomify.com/CVE-2026-0707/index.md","name":"CVE-2026-0707","record":{"aliases":["GHSA-gv94-wp4h-vv8p"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Keycloak identity server","requires_auth":"none","summary":"Attackers can bypass security controls by exploiting overly permissive Bearer token header parsing in Keycloak.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-551","name":"Incorrect Behavior Order: Authorization Before Parsing and Canonicalization"}],"description":"A flaw was found in Keycloak. The Keycloak Authorization header parser is overly permissive regarding the formatting of the \"Bearer\" authentication scheme. It accepts non-standard characters (such as tabs) as separators and tolerates case variations that deviate from RFC 6750 specifications.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Keycloak: keycloak authorization header parsing leading to potential security control bypass","id":"CVE-2026-0707","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":2,"n_references":5,"next":{"headline":"Libucl: libucl: denial of service via embedded null byte in ucl input","id":"CVE-2026-0708"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["26.5.0"],"package":"org.keycloak:keycloak-parent","purl":null,"source":"GHSA-gv94-wp4h-vv8p"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["26.5.0"],"package":"org.keycloak:keycloak-parent","purl":"pkg:maven/org.keycloak/keycloak-parent","source":"GHSA-gv94-wp4h-vv8p"}],"prev":{"headline":"Privilege escalation in Acronis Cloud Manager","id":"CVE-2026-0705"},"products":["Red Hat build of Keycloak 26.4","Red Hat build of Keycloak 26.4.10"],"published":"2026-01-08","related":[],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-08","vendors":["Red Hat"]},"summary":"Attackers can bypass security controls by exploiting overly permissive Bearer token header parsing in Keycloak.","url":"https://insights.sbomify.com/CVE-2026-0707/"}