{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-107909 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-107909 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-107909 is a high-severity memory corruption vulnerability in FalkorDB, published on 9 Oct 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-107909 and fix it if it is affected.\n\nWhat it is: CVE-2026-107909 is a high-severity memory corruption vulnerability in FalkorDB, published on 9 Oct 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-107909 in the wild and no public exploit code.\n\nAffected product: FalkorDB. 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-107909/ (Markdown: https://insights.sbomify.com/CVE-2026-107909/index.md)","id":"CVE-2026-107909","markdown":"https://insights.sbomify.com/CVE-2026-107909/index.md","name":"CVE-2026-107909","record":{"aliases":["GHSA-x67x-q5pm-p9h7"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"FalkorDB database","requires_auth":"none","summary":"Remote unauthenticated attackers can cause denial of service or potential code execution via heap corruption in FalkorDB's Bolt WebSocket handling when the Bolt endpoint is enabled.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"securin","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"A heap-based out-of-bounds write in the ws_read_frame function (src/bolt/ws.c) and the buffer_apply_mask function (src/bolt/buffer.c) in FalkorDB before 4.20.0 allows a remote unauthenticated attacker to cause a denial of service and possibly corrupt heap memory by sending a WebSocket frame with a 64-bit extended payload length to the Bolt port. The payload length is not bounded, and the only bounds check in buffer_apply_mask is an ASSERT(), which is compiled out in release builds, so the function XORs memory beyond the end of the receive buffer with the attacker-supplied mask key. Only deployments that enable the Bolt endpoint (BOLT_PORT, disabled by default) are affected.","ecosystems":[],"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":"Pre-authentication heap out-of-bounds write in FalkorDB Bolt WebSocket frame handling via unbounded payload length","id":"CVE-2026-107909","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Authentication bypass in FalkorDB Bolt endpoint via fail-open AUTH probe error handling","id":"CVE-2026-107910"},"packages":[],"prev":{"headline":"Pre-authentication heap out-of-bounds write in FalkorDB Bolt BoltReadHandler via RESET message","id":"CVE-2026-107908"},"products":["FalkorDB"],"published":"2026-10-09","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"total"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["FalkorDB"]},"summary":"Remote unauthenticated attackers can cause denial of service or potential code execution via heap corruption in FalkorDB's Bolt WebSocket handling when the Bolt endpoint is enabled.","url":"https://insights.sbomify.com/CVE-2026-107909/"}