Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Versions 1.4.0 up to but not including 2.9.6 of the sqlite3 RubyGems package are affected. When an aggregate function with two or more arguments is defined and then run over TEXT or BLOB column values, garbage collection can free argument objects still in use, so the aggregate's step method may receive a wrong object or the process may crash. Upgrade to sqlite3 2.9.6 or later; no reliable workaround is listed, so avoid multi-argument aggregates if you cannot upgrade.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| Not published | None | 4.0 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N | GitHub Advisory Database |
- CISA KEV Not listed.
- EPSS No score.
Timeline
- 31 Oct 2026, 14:21 UTC First seen by agentprime
- 31 Oct 2026, 14:21 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-mwm8-39rw-8826
- OSV: GHSA-mwm8-39rw-8826
- github.com/sparklemotion/sqlite3-ruby/security/advisories/GHSA-mwm8-39rw-8826
- github.com/sparklemotion/sqlite3-ruby/pull/733
- github.com/sparklemotion/sqlite3-ruby/commit/cc5ac0cdf05af8148f4363410da0ba32508d9c97
- github.com/sparklemotion/sqlite3-ruby
- github.com/sparklemotion/sqlite3-ruby/releases/tag/v2.9.6