Update dependency sqlite3 to v2 [SECURITY] - #30
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
|
Tick the box to add this pull request to the merge queue (same as
|
renovate
Bot
force-pushed
the
renovate/rubygems-sqlite3-vulnerability
branch
from
August 26, 2026 22:27
2a8dbde to
f8e5ba8
Compare
renovate
Bot
force-pushed
the
renovate/rubygems-sqlite3-vulnerability
branch
6 times, most recently
from
September 8, 2026 01:53
ebba696 to
74413e4
Compare
renovate
Bot
force-pushed
the
renovate/rubygems-sqlite3-vulnerability
branch
6 times, most recently
from
September 16, 2026 22:38
da2a4d8 to
3194c1c
Compare
renovate
Bot
force-pushed
the
renovate/rubygems-sqlite3-vulnerability
branch
from
September 17, 2026 22:30
3194c1c to
427fda9
Compare
renovate
Bot
force-pushed
the
renovate/rubygems-sqlite3-vulnerability
branch
from
September 18, 2026 03:04
427fda9 to
e9f8509
Compare
This PR contains the following updates:
"~> 1.4"→"~> 2.9", ">= 2.9.5"SQLite3 addresses vulnerability in packaged version of libsqlite
GHSA-mgvv-5mxp-xq67
More information
Details
Summary
The rubygem sqlite3 v1.5.1 upgrades the packaged version of libsqlite from v3.39.3 to v3.39.4.
libsqlite v3.39.4 addresses a vulnerability described as follows in the release notification:
This vulnerability has not been assigned a CVE and does not have a severity declared.
Please note that this advisory only applies to the sqlite3 gem v1.5.0, and only if the packaged libsqlite is being used. If you've overridden defaults at installation time to use system libraries instead of packaged libraries, you should instead pay attention to your distro's libsqlite release announcements.
Mitigation
Upgrade to the rubygem sqlite3 v1.5.1 or later.
Users who are unable to upgrade the sqlite3 gem may also choose a more complicated mitigation: compile and link sqlite3 against external libsqlite >= 3.39.4 which will also address these same issues.
References
Severity
Low
References
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
sqlite3-ruby has Use-After-Free When Redefining SQLite Functions with Different Arity
CVE-2026-54619 / GHSA-28hh-pr2h-2w89
More information
Details
Summary
Using
Database#create_functionorDatabase#define_functionto define the same function name more than once with different numbers of arguments ("arity") or text encodings will result in a invalid memory read and a segmentation fault.Mitigation
Upgrade to sqlite3 gem v2.9.5 or later.
As a workaround, avoid defining multiple custom functions with the same name (varying numbers of arguments or encoding).
Severity
The sqlite3-ruby maintainers assess this as Low severity. It is reliably triggered after GC when code is structured in a particular way. There is no known general exploit that could be used as a denial of service attack.
Severity
CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.