CVE-2026-54619

LOWPre-NVD 2.02.0
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 99% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
2.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 2.0Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

sqlite3 provides Ruby bindings for the SQLite3 embedded database. In version 2.9.4 and earlier, redefining a SQLite function with a different arity frees the previously registered function handler while SQLite may still reference it, resulting in a use-after-free. This issue is fixed in version 2.9.5.

CVSS v3
2.0
EG Score
2.0(medium)
EG Risk
9(Track)
EG Risk 9/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity20% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

July 28, 2026

Last Modified

July 30, 2026

Vendor Advisories for CVE-2026-54619(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(6 across 5 ecosystems)
RubyGems(2)
PackageVulnerable rangeFixed inDependents
sqlite30.0.0 ... 2.9.4 (83 versions)2.9.5
sqlite3-ruby0.5.0 ... 1.3.3.beta.1 (19 versions)2.9.5
Debian:11(1)
PackageVulnerable rangeFixed inDependents
ruby-sqlite31.4.2-3 ... 2.9.5-2 (11 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
ruby-sqlite31.4.2-4 ... 2.9.5-2 (10 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
ruby-sqlite31.7.3-1 ... 2.9.5-2 (7 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
ruby-sqlite31.7.3-1, 1.7.3-2, 2.9.0-1, 2.9.1-1, 2.9.3-12.9.5-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 36× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-23 00:19 UTCEPSS rescore
  2. 2026-08-21 23:49 UTCEPSS rescore
  3. 2026-08-21 17:16 UTCEG score recompute
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-19 17:04 UTCEPSS rescore
  6. 2026-08-18 23:35 UTCEG score recompute
  7. 2026-08-18 13:48 UTCEPSS rescore
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-16 14:56 UTCEPSS rescore
  10. 2026-08-16 05:53 UTCEG score recompute
  11. 2026-08-16 02:14 UTCEPSS rescore
  12. 2026-08-15 01:30 UTCEPSS rescore
  13. 2026-08-13 22:00 UTCEPSS rescore
  14. 2026-08-13 12:12 UTCEG score recompute
  15. 2026-08-12 13:51 UTCEPSS rescore
  16. 2026-08-11 00:00 UTCEPSS rescore
  17. 2026-08-10 18:31 UTCEG score recompute
  18. 2026-08-09 13:46 UTCEPSS rescore
  19. 2026-08-08 16:37 UTCEPSS rescore
  20. 2026-08-08 00:50 UTCEG score recompute
  21. 2026-08-06 13:47 UTCEPSS rescore
  22. 2026-08-05 19:17 UTCEPSS rescore
  23. 2026-08-05 07:10 UTCEG score recompute
  24. 2026-08-04 15:10 UTCEPSS rescore
  25. 2026-08-04 10:39 UTCEPSS rescore
Show 11 more
  1. 2026-08-03 10:36 UTCEPSS rescore
  2. 2026-08-02 13:25 UTCEG score recompute
  3. 2026-08-01 04:16 UTCEPSS rescore
  4. 2026-07-30 19:44 UTCEG score recompute
  5. 2026-07-30 16:28 UTCEPSS rescore
  6. 2026-07-30 01:30 UTCEPSS rescore
  7. 2026-07-28 20:26 UTCEG score recompute
  8. 2026-07-28 20:06 UTCEG score recompute
  9. 2026-07-28 17:22 UTCEG score recompute 2.00
  10. 2026-07-28 17:21 UTCNVD updateCVSS v3 → 2 · CVSS v4 → 2
  11. 2026-07-28 16:24 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-54619?
CVE-2026-54619 is a low vulnerability published on July 28, 2026. sqlite3 provides Ruby bindings for the SQLite3 embedded database. In version 2.9.4 and earlier, redefining a SQLite function with a different arity frees the previously registered function handler while SQLite may still reference it, resulting in a use-after-free. This issue is fixed in version…
When was CVE-2026-54619 disclosed?
CVE-2026-54619 was first published in the National Vulnerability Database on July 28, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54619 actively exploited?
CVE-2026-54619 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.7% of all scored CVEs.
What is the CVSS score of CVE-2026-54619?
CVE-2026-54619 has a CVSS v3 base score of 2.0 (NVD).
How do I remediate CVE-2026-54619?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54619, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54619

Explore →

Is Your Infrastructure Affected by CVE-2026-54619?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.