{"answers":{"affected":"2 open source packages ship an affected version, including surrealdb-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-63733 in the wild and no public exploit code.","fix":"Upgrade surrealdb-core to 3.2.0 or later.","what":"CVE-2026-63733 is a medium-severity missing authorization vulnerability in Surrealdb Surrealdb, published on 20 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-63733 and fix it if it is affected.\n\nWhat it is: CVE-2026-63733 is a medium-severity missing authorization vulnerability in Surrealdb Surrealdb, published on 20 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-63733 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- surrealdb-core (crates.io): affected all versions; fixed in 3.2.0\n- surrealdb-core (crates.io): affected all versions; fixed in 3.2.0\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-63733/ (Markdown: https://insights.sbomify.com/CVE-2026-63733/index.md)","id":"CVE-2026-63733","markdown":"https://insights.sbomify.com/CVE-2026-63733/index.md","name":"CVE-2026-63733","record":{"aliases":["GHSA-66r2-5gwj-gxm2"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["data_modify","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"SurrealDB database","requires_auth":"low_privilege","summary":"Attackers can bypass table permissions by embedding write statements in PERMISSIONS clauses, allowing unauthorized data modification.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"surrealdb","vendor":"surrealdb"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"SurrealDB versions before 3.2.0 contain a permissions bypass vulnerability where data-modifying statements within PERMISSIONS clauses execute with enforcement disabled. Attackers with permission to perform a guarded operation can write to tables they lack permission for by embedding CREATE, UPDATE, DELETE, or UPSERT statements in the PERMISSIONS clause, causing unintended writes and data corruption.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"SurrealDB before 3.2.0 Permissions Bypass via PERMISSIONS Clause","id":"CVE-2026-63733","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":"surrealdb:surrealdb","products":["surrealdb:surrealdb"],"type":"missing_authorization","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"SurrealDB before 3.2.0 Denial of Service via malformed SurrealML import","id":"CVE-2026-63734"},"packages":[{"ecosystem":"crates.io","fixed":["3.2.0"],"introduced":["0"],"last_affected":[],"package":"surrealdb-core","purl":null,"source":"GHSA-66r2-5gwj-gxm2"},{"ecosystem":"crates.io","fixed":["3.2.0"],"introduced":["0"],"last_affected":[],"package":"surrealdb-core","purl":"pkg:cargo/surrealdb-core","source":"GHSA-66r2-5gwj-gxm2"}],"prev":{"headline":"9router before 0.4.60 Remote Code Execution via default password","id":"CVE-2026-63732"},"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":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"Attackers can bypass table permissions by embedding write statements in PERMISSIONS clauses, allowing unauthorized data modification.","url":"https://insights.sbomify.com/CVE-2026-63733/"}