{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-63736 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-63736 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-63736 is a medium-severity server-side request forgery vulnerability in Surrealdb Surrealdb, published on 20 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-63736 and fix it if it is affected.\n\nWhat it is: CVE-2026-63736 is a medium-severity server-side request forgery vulnerability in Surrealdb Surrealdb, published on 20 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-63736 in the wild and no public exploit code.\n\nAffected product: Surrealdb Surrealdb. 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-63736/ (Markdown: https://insights.sbomify.com/CVE-2026-63736/index.md)","id":"CVE-2026-63736","markdown":"https://insights.sbomify.com/CVE-2026-63736/index.md","name":"CVE-2026-63736","record":{"aliases":["GHSA-qrjc-jcj4-56p7"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"SurrealDB database","requires_auth":"high_privilege","summary":"An Owner role attacker can exploit a hostname validation flaw in SurrealDB's JWKS fetcher to force the server to make requests to internal private or loopback addresses.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"surrealdb","vendor":"surrealdb"}],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"SurrealDB before 3.2.0 contains a server-side request forgery vulnerability in the JWKS fetcher that validates only the URL hostname string against allow-lists without checking resolved IP addresses. An Owner role attacker can point an access method at an allow-listed hostname resolving to private or loopback addresses, causing the server to issue GET requests to internal addresses that would be blocked by direct URL.","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":"SurrealDB before 3.2.0 SSRF via JWKS URL hostname resolution","id":"CVE-2026-63736","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"surrealdb:surrealdb","products":["surrealdb:surrealdb"],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"SurrealDB before 3.1.5 Denial of Service via deep operator chains","id":"CVE-2026-63737"},"packages":[],"prev":{"headline":"SurrealDB before 3.2.0 Authentication Bypass via Custom API","id":"CVE-2026-63735"},"products":["surrealdb"],"published":"2026-07-20","related":[{"cvss_score":9.4,"headline":"SurrealDB before 2.2.2 SurrealQL Injection via export","id":"CVE-2025-71392","kev_date_added":null,"published":"2026-07-18"},{"cvss_score":9.2,"headline":"SurrealDB before 3.1.0 Privilege Escalation via RPC Session Race Condition","id":"CVE-2026-63756","kev_date_added":null,"published":"2026-07-20"},{"cvss_score":8.7,"headline":"SurrealDB before 3.1.0 Denial of Service via malformed RPC use","id":"CVE-2026-63747","kev_date_added":null,"published":"2026-07-20"},{"cvss_score":8.7,"headline":"SurrealDB before 3.1.0 Session Hijacking via /rpc sessions","id":"CVE-2026-63757","kev_date_added":null,"published":"2026-07-20"},{"cvss_score":8.7,"headline":"SurrealDB before 3.1.0 Denial of Service via JSON Parser","id":"CVE-2026-63760","kev_date_added":null,"published":"2026-07-20"},{"cvss_score":8.7,"headline":"SurrealDB before 1.0.1 Insecure Default Table Permissions","id":"CVE-2023-54366","kev_date_added":null,"published":"2026-07-18"},{"cvss_score":8.7,"headline":"SurrealDB before 1.5.5 Query Injection via RPC API","id":"CVE-2024-58362","kev_date_added":null,"published":"2026-07-18"}],"sources":[{"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-07-28","vendors":["surrealdb"]},"summary":"An Owner role attacker can exploit a hostname validation flaw in SurrealDB's JWKS fetcher to force the server to make requests to internal private or loopback addresses.","url":"https://insights.sbomify.com/CVE-2026-63736/"}