{"answers":{"affected":"2 open source packages ship an affected version, including org.keycloak:keycloak-parent.","exploited":"There is no known exploitation of CVE-2026-1518 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-1518 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-1518 is a vulnerability in org.keycloak:keycloak-parent, published on 2 Feb 2026."},"fix_prompt":"Check this codebase for CVE-2026-1518 and fix it if it is affected.\n\nWhat it is: CVE-2026-1518 is a vulnerability in org.keycloak:keycloak-parent, published on 2 Feb 2026. \nExploitation: There is no known exploitation of CVE-2026-1518 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.2; no fix listed\n- org.keycloak:keycloak-parent (Maven): affected all versions up to 26.5.2; 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-1518/ (Markdown: https://insights.sbomify.com/CVE-2026-1518/index.md)","id":"CVE-2026-1518","markdown":"https://insights.sbomify.com/CVE-2026-1518/index.md","name":"CVE-2026-1518","record":{"aliases":["GHSA-fwhw-chw4-gh37"],"analysis":null,"analysis_generated_by":null,"assigner":"redhat","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"DO NOT USE THIS CANDIDATE NUMBER. After further review by the Keycloak project and Red Hat, the reported SSRF via client registration/backchannel notification URIs was determined not to constitute a security vulnerability. The reported behavior is expected administrator-controlled functionality, and Keycloak provides documented mitigations through Client Policies, including the Secure Client URIs Pattern executor. Therefore, this CVE has been rejected.","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 Server-Side Request Forgery (SSRF) vulnerability","id":"CVE-2026-1518","indexable":false,"kev":null,"kind":"cve_rejected","links":{"ecosystem":"Maven","product":null,"products":[],"type":null,"year":"2026"},"n_packages":2,"n_references":0,"next":{"headline":"Excessive NSEC3 iterations cause high CPU load during insecure delegation validation","id":"CVE-2026-1519"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["26.5.2"],"package":"org.keycloak:keycloak-parent","purl":null,"source":"GHSA-fwhw-chw4-gh37"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["26.5.2"],"package":"org.keycloak:keycloak-parent","purl":"pkg:maven/org.keycloak/keycloak-parent","source":"GHSA-fwhw-chw4-gh37"}],"prev":{"headline":"iomad Company Admin Block sql injection","id":"CVE-2026-1517"},"products":[],"published":"2026-02-02","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"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"REJECTED","updated":"2026-07-24","vendors":[]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-1518/"}