{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-51936 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-51936 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-51936 is a low-severity SQL injection vulnerability in Zetetic SQLCipher, published on 30 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-51936 and fix it if it is affected.\n\nWhat it is: CVE-2026-51936 is a low-severity SQL injection vulnerability in Zetetic SQLCipher, published on 30 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-51936 in the wild and no public exploit code.\n\nAffected product: Zetetic SQLCipher. 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-51936/ (Markdown: https://insights.sbomify.com/CVE-2026-51936/index.md)","id":"CVE-2026-51936","markdown":"https://insights.sbomify.com/CVE-2026-51936/index.md","name":"CVE-2026-51936","record":{"aliases":["GHSA-7w4j-532w-pgpj"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"SQLCipher encryption library","requires_auth":"none","summary":"Attackers can exploit SQLCipher's export function to bypass defensive restrictions, modify schema tables, and corrupt databases via crafted source names.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":2.1,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:L","version":"4.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"Zetetic SQLCipher before 4.15.0 allows SQL injection. The sqlcipher_export convenience function can be used to copy the contents of one attached database into another. It is most often used to convert between plaintext and encrypted databases. It needs to do dynamic schema manipulation, and thus the function temporarily clears defensive restrictions during operation. A vulnerability in the handling of the source database name parameter made it possible for a caller to supply a crafted source name, which could execute statements that defensive mode would otherwise block. This could allow direct modifications to the sqlite_schema table and database corruption. SQLCipher 4.15.0 now strictly validates the source database name and prevents the bypass.","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":"SQL injection in SQLCipher","id":"CVE-2026-51936","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in n/a","id":"CVE-2026-51937"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2026-51934"},"products":["SQLCipher"],"published":"2026-09-30","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-02","vendors":["Zetetic"]},"summary":"Attackers can exploit SQLCipher's export function to bypass defensive restrictions, modify schema tables, and corrupt databases via crafted source names.","url":"https://insights.sbomify.com/CVE-2026-51936/"}