How severe is CVE-2026-54620?

No CVSS score has been assigned to CVE-2026-54620 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-54620?

CVE-2026-54620 affects the following packages: sqlite3-ruby (RubyGems), sqlite3 (RubyGems). Ecosystems affected: RubyGems.

How do I fix CVE-2026-54620?

Update sqlite3-ruby to 2.9.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-54620 is resolved across your whole dependency graph.

How do I detect CVE-2026-54620 in my RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sqlite3-ruby. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2026-54620 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2026-54620?

O3 pinpoints whether CVE-2026-54620 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2026-54620 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-54620 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is CVE-2026-54620?

CVE-2026-54620 is classified as Use After Free (CWE-416). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-54620 published, and has it been updated?

CVE-2026-54620 was published on July 28, 2026 and was last updated on July 29, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

💎 RubyGems

CVE-2026-54620

CVE-2026-54620 is a Use After Free vulnerability in sqlite3-ruby. O3 Security confirms whether CVE-2026-54620 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

sqlite3-ruby has Use-After-Free in SQLite Aggregate Function Callbacks

Also known asGHSA-j7fr-3v8c-3qc3

Published

Jul 28, 2026

Updated

Jul 29, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Blast Radius

2 pkgs affected

💎sqlite3-ruby💎sqlite3

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

sqlite3 provides Ruby bindings for the SQLite3 embedded database. From 2.1.0 to 2.9.4, the callbacks used for SQLite aggregate functions can be freed while still referenced during aggregation, resulting in a use-after-free. This issue is fixed in version 2.9.5.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`sqlite3-ruby`	≥ 2.1.0&&< 2.9.5	2.9.5
💎RubyGems	`sqlite3`	≥ 2.1.0&&< 2.9.5	2.9.5

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sqlite3-ruby. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update sqlite3-ruby to 2.9.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-54620 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-54620 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2026-54620. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-54620 in your dependencies?

O3 detects CVE-2026-54620 across RubyGems dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works