{"answers":{"affected":"2 open source packages ship an affected version, including org.keycloak:keycloak-adapter-core.","exploited":"There is no known exploitation of CVE-2026-1180 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-1180 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-1180 is a medium-severity server-side request forgery vulnerability in Red Hat Build of Keycloak, published on 20 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-1180 and fix it if it is affected.\n\nWhat it is: CVE-2026-1180 is a medium-severity server-side request forgery vulnerability in Red Hat Build of Keycloak, published on 20 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-1180 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.keycloak:keycloak-adapter-core (Maven): affected all versions up to 25.0.3; no fix listed\n- org.keycloak:keycloak-adapter-core (Maven): affected all versions up to 25.0.3; 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-1180/ (Markdown: https://insights.sbomify.com/CVE-2026-1180/index.md)","id":"CVE-2026-1180","markdown":"https://insights.sbomify.com/CVE-2026-1180/index.md","name":"CVE-2026-1180","record":{"aliases":["GHSA-7vw6-5q2f-7w5r"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Keycloak identity server","requires_auth":"none","summary":"Attackers can force Keycloak to make arbitrary HTTP requests via jwks_uri, enabling internal network probing and cloud metadata access.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":5.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"A flaw was identified in Keycloak’s OpenID Connect Dynamic Client Registration feature when clients authenticate using private_key_jwt. The issue allows a client to specify an arbitrary jwks_uri, which Keycloak then retrieves without validating the destination. This enables attackers to coerce the Keycloak server into making HTTP requests to internal or restricted network resources. As a result, attackers can probe internal services and cloud metadata endpoints, creating an information disclosure and reconnaissance risk.","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’s OpenID Connect Dynamic Client Registration feature affected by Server-Side Request Forgery (SSRF)","id":"CVE-2026-1180","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"Altium 365 Over-Permissive CORS Configuration Allows Credentialed Cross-Origin Workspace Access","id":"CVE-2026-1181"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["25.0.3"],"package":"org.keycloak:keycloak-adapter-core","purl":null,"source":"GHSA-7vw6-5q2f-7w5r"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["25.0.3"],"package":"org.keycloak:keycloak-adapter-core","purl":"pkg:maven/org.keycloak/keycloak-adapter-core","source":"GHSA-7vw6-5q2f-7w5r"}],"prev":{"headline":"Yonyou KSOA HTTP GET Parameter user_popedom.jsp sql injection","id":"CVE-2026-1179"},"products":["Red Hat Build of Keycloak","Red Hat JBoss Enterprise Application Platform 8","Red Hat JBoss Enterprise Application Platform Expansion Pack","Red Hat Single Sign-On 7","Red Hat build of Keycloak 26.4","Red Hat build of Keycloak 26.4.11"],"published":"2026-01-20","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-04-02","vendors":["Red Hat"]},"summary":"Attackers can force Keycloak to make arbitrary HTTP requests via jwks_uri, enabling internal network probing and cloud metadata access.","url":"https://insights.sbomify.com/CVE-2026-1180/"}