{"answers":{"affected":"1 open source package ship an affected version, including valkey.","exploited":"There is no known exploitation of CVE-2026-56684 in the wild and no public exploit code.","fix":"Upgrade valkey to a fixed version for your release line: 7.2.14, 8.0.10, 8.1.9 or 9.0.5.","what":"CVE-2026-56684 is a high-severity use after free vulnerability in valkey-io valkey, published on 18 Aug 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-56684 and fix it if it is affected.\n\nWhat it is: CVE-2026-56684 is a high-severity use after free vulnerability in valkey-io valkey, published on 18 Aug 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-56684 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- valkey (Bitnami): affected all versions; fixed in 7.2.14, 8.0.10, 8.1.9, 9.0.5, 9.1.1\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-56684/ (Markdown: https://insights.sbomify.com/CVE-2026-56684/index.md)","id":"CVE-2026-56684","markdown":"https://insights.sbomify.com/CVE-2026-56684/index.md","name":"CVE-2026-56684","record":{"aliases":["AZL-96888","BELL-CVE-2026-56684","BIT-valkey-2026-56684","DEBIAN-CVE-2026-56684","GHSA-53mc-f3m3-99vh","UBUNTU-CVE-2026-56684"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Valkey database","requires_auth":"low_privilege","summary":"An authenticated attacker can trigger a use-after-free in Valkey's TLS processing, potentially leading to remote code execution or server crashes.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-416","name":"Use After Free"}],"description":"Valkey is a distributed key-value database. Prior to 7.2.14, 8.0.10, 8.1.9, 9.0.5, and 9.1.1, Valkey's tlsProcessPendingData function iterates pending_list while an authenticated client can trigger CLIENT KILL, causing connTLSClose to delete the iterator's cached next node and producing a use-after-free that can crash the server or potentially allow remote code execution when TLS is enabled. This issue is fixed in versions 7.2.14, 8.0.10, 8.1.9, 9.0.5, and 9.1.1.","ecosystems":["Bitnami"],"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":"Valkey: TLS pending-data processing use-after-free may allow remote code execution","id":"CVE-2026-56684","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":1,"n_references":8,"next":{"headline":"Command injection in ObjectScale","id":"CVE-2026-56685"},"packages":[{"ecosystem":"Bitnami","fixed":["7.2.14","8.0.10","8.1.9","9.0.5","9.1.1"],"introduced":["0","8.0.0","8.1.0","9.0.0","9.1.0"],"last_affected":[],"package":"valkey","purl":"pkg:bitnami/valkey","source":"BIT-valkey-2026-56684"}],"prev":{"headline":"9Router: Login Brute-Force Lockout Bypass via Spoofable X-9r-Real-Ip Header","id":"CVE-2026-56682"},"products":["valkey"],"published":"2026-08-18","related":[],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-19","vendors":["valkey-io"]},"summary":"An authenticated attacker can trigger a use-after-free in Valkey's TLS processing, potentially leading to remote code execution or server crashes.","url":"https://insights.sbomify.com/CVE-2026-56684/"}