{"answers":{"affected":"2 open source packages ship an affected version, including sqlite3.","exploited":"There is no known exploitation of GHSA-mwm8-39rw-8826 in the wild and no public exploit code.","fix":"Upgrade sqlite3 to 2.9.6 or later.","what":"GHSA-mwm8-39rw-8826 is an use after free vulnerability in sqlite3, published on 2 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 GHSA-mwm8-39rw-8826 and fix it if it is affected.\n\nWhat it is: GHSA-mwm8-39rw-8826 is an use after free vulnerability in sqlite3, published on 2 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 GHSA-mwm8-39rw-8826 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- sqlite3 (RubyGems): affected from 1.4.0; fixed in 2.9.6\n- sqlite3 (RubyGems): affected from 1.4.0; fixed in 2.9.6\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/GHSA-mwm8-39rw-8826/ (Markdown: https://insights.sbomify.com/GHSA-mwm8-39rw-8826/index.md)","id":"GHSA-mwm8-39rw-8826","markdown":"https://insights.sbomify.com/GHSA-mwm8-39rw-8826/index.md","name":"GHSA-mwm8-39rw-8826","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","other"],"network_reachable":"yes","non_default_config":false,"product_category":"Ruby SQLite library","requires_auth":"none","summary":"A use-after-free in sqlite3-ruby allows attackers to cause crashes or incorrect data processing by influencing TEXT or BLOB column sizes in multi-argument aggregates.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"## Summary\n\nUsing `Database#create_aggregate`, `#create_aggregate_handler`, or `Database#define_aggregator` to define an aggregate function that takes two or more arguments, and then evaluating it over TEXT or BLOB column values, can free the Ruby objects holding those arguments while a later argument is still being converted, during ordinary garbage collection. The aggregate's `step` method then receives an incorrect object, or the process crashes with a segmentation fault.\n\n## Mitigation\n\nUpgrade to sqlite3 gem v2.9.6 or later.\n\nThere is no reliable workaround. If you cannot upgrade, avoid defining aggregate functions that take two or more arguments. Restricting column value sizes is not a mitigation: smaller values make the defect fire less often but do not prevent it.\n\n## Severity\n\nThe sqlite3-ruby maintainers assess this as Medium severity (CVSS 4.0 score 6.3). It is reached through ordinary garbage collection without any unusual code structuring: an application is exposed whenever it evaluates a multi-argument aggregate over TEXT or BLOB values whose size an attacker can influence. The demonstrated impact is an incorrect value passed to the aggregate's `step` method, or a process crash; no controlled memory write or general denial-of-service exploit has been demonstrated.\n\n## Credits\n\nReported by Jeremy Daer ([@jeremy](https://github.com/jeremy)).","ecosystems":["RubyGems"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"sqlite3-ruby: Use-After-Free in SQLite Aggregate Arguments in Heap-Allocated Argument Array","id":"GHSA-mwm8-39rw-8826","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"RubyGems","fixed":["2.9.6"],"introduced":["1.4.0"],"last_affected":[],"package":"sqlite3","purl":null,"source":"GHSA-mwm8-39rw-8826"},{"ecosystem":"RubyGems","fixed":["2.9.6"],"introduced":["1.4.0"],"last_affected":[],"package":"sqlite3","purl":"pkg:gem/sqlite3","source":"GHSA-mwm8-39rw-8826"}],"products":null,"published":"2026-10-02","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"A use-after-free in sqlite3-ruby allows attackers to cause crashes or incorrect data processing by influencing TEXT or BLOB column sizes in multi-argument aggregates.","url":"https://insights.sbomify.com/GHSA-mwm8-39rw-8826/"}