Answer in brief
CVE-2026-54619 records a Low severity security vulnerability in sqlite3-ruby has Use-After-Free When Redefining SQLite Functions with Different Arity. The source record does not mark it as known exploited. 2 affected packages are mapped in the feed.
Answer in brief
CVE-2026-54619 records a Low severity security vulnerability in sqlite3-ruby has Use-After-Free When Redefining SQLite Functions with Different Arity. The source record does not mark it as known exploited. 2 affected packages are mapped in the feed.
Update sqlite3 to 2.9.5; sqlite3-ruby to 2.9.5 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanVulnerability describes the vulnerability class recorded for this advisory. The current record does not mark CVE-2026-54619 as known exploited; continue to monitor the source for status changes. The feed includes package mappings that can be checked against lockfiles and deployed manifests.
| Package | Affected range | Fixed version |
|---|---|---|
| sqlite3rubygems | <=2.9.4 | 2.9.5 |
| sqlite3-rubyrubygems | <=2.9.4 | 2.9.5 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
CVE-2026-54619 records a Low severity security vulnerability in sqlite3-ruby has Use-After-Free When Redefining SQLite Functions with Different Arity. The source record does not mark it as known exploited. 2 affected packages are mapped in the feed.
The source record does not mark it as known exploited.
Check lockfiles and deployed manifests for sqlite3, sqlite3-ruby.
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL GuardUpdate sqlite3 to 2.9.5; sqlite3-ruby to 2.9.5 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanVulnerability describes the vulnerability class recorded for this advisory. The current record does not mark CVE-2026-54619 as known exploited; continue to monitor the source for status changes. The feed includes package mappings that can be checked against lockfiles and deployed manifests.
| Package | Affected range | Fixed version |
|---|---|---|
| sqlite3rubygems | <=2.9.4 | 2.9.5 |
| sqlite3-rubyrubygems | <=2.9.4 | 2.9.5 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
CVE-2026-54619 records a Low severity security vulnerability in sqlite3-ruby has Use-After-Free When Redefining SQLite Functions with Different Arity. The source record does not mark it as known exploited. 2 affected packages are mapped in the feed.
The source record does not mark it as known exploited.
Check lockfiles and deployed manifests for sqlite3, sqlite3-ruby.
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard## Summary Using `Database#create_function` or `Database#define_function` to 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.
## Summary Using `Database#create_function` or `Database#define_function` to 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.