Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-54620

Use-After-Free in sqlite3-ruby (CVE-2026-54620)

Summary

Vulnerability in sqlite3-ruby (CVE-2026-54620). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.9.5 or later.

Original description

The description as published by the source.

Summary

Using Database#create_aggregate, #create_aggregate_handler, or Database#define_aggregator to define an aggregate function, and then using an open statement calling that function after the database has been explicitly closed will result in an invalid memory read and a segmentation fault.

Mitigation

Upgrade to sqlite3 gem v2.9.5 or later.

As a workaround, avoid using an aggregate function after closing the database.

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.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-54620 has been found in sqlite3-ruby.
Risk of unauthorized operations or information disclosure.
What to do: upgrade sqlite3-ruby to 2.9.5 or later.
If unsure, ask your IT team or search "sqlite3-ruby CVE-2026-54620" on the vendor's site.

CVE-2026-54620 (sqlite3-ruby) — CWE-416
Patched: 2.9.5 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Use-after-free (CWE-416) exists in sqlite3-ruby.

📍 Affected scope

Check the vendor advisory for the affected versions of sqlite3-ruby.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.9.5.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'sqlite3-ruby' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'sqlite3-ruby' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で sqlite3-ruby を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade sqlite3-ruby to 2.9.5

    ステージング環境で 2.9.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

rubygems sqlite3-ruby
[{"type":"ECOSYSTEM","events":[{"introduced":"2.1.0"},{"fixed":"2.9.5"}]}]
rubygems sqlite3
[{"type":"ECOSYSTEM","events":[{"introduced":"2.1.0"},{"fixed":"2.9.5"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details