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% (2nd percentile of EPSS-scored CVEs). 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.1%CVSS: 2.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.0LOWmedium confidence
EG Risk
9
EG Risk 9/100CISA SSVC

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%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 28, 2026

Last Modified

July 30, 2026

References (4)

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 rangeFix by version rangeDependents
sqlite30.0.0 ... 2.9.4 (83 versions)
  • every version up to 2.9.5: fixed in 2.9.5
—
sqlite3-ruby0.5.0 ... 1.3.3.beta.1 (19 versions)
  • every version up to 2.9.5: fixed in 2.9.5
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
ruby-sqlite31.4.2-3 ... 2.9.5-2 (11 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
ruby-sqlite31.4.2-4 ... 2.9.6-2 (12 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
ruby-sqlite31.7.3-1 ... 2.9.6-2 (9 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
ruby-sqlite31.7.3-1, 1.7.3-2, 2.9.0-1, 2.9.1-1, 2.9.3-1
  • every version up to 2.9.5-1: fixed in 2.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 / 30× 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-10-07 01:25 UTCEG score recompute
  2. 2026-10-06 15:18 UTCEPSS rescore
  3. 2026-10-05 17:43 UTCEPSS rescore
  4. 2026-10-04 23:22 UTCEPSS rescore
  5. 2026-10-04 07:09 UTCEG score recompute
  6. 2026-10-03 14:26 UTCEPSS rescore
  7. 2026-10-02 17:56 UTCEPSS rescore
  8. 2026-10-01 19:50 UTCEPSS rescore
  9. 2026-10-01 03:43 UTCEG score recompute
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-29 15:22 UTCEPSS rescore
  12. 2026-09-28 13:51 UTCEPSS rescore
  13. 2026-09-28 03:23 UTCEG score recompute
  14. 2026-09-27 13:48 UTCEPSS rescore
  15. 2026-09-26 15:59 UTCEPSS rescore
  16. 2026-09-24 14:04 UTCEPSS rescore
  17. 2026-09-23 17:54 UTCEPSS rescore
  18. 2026-09-22 21:41 UTCEG score recompute
  19. 2026-09-20 20:16 UTCEPSS rescore
  20. 2026-09-19 00:06 UTCEG score recompute
  21. 2026-09-18 19:28 UTCEPSS rescore
  22. 2026-09-17 19:31 UTCEPSS rescore
  23. 2026-09-16 14:08 UTCEPSS rescore
  24. 2026-09-16 05:53 UTCEG score recompute
  25. 2026-09-15 03:11 UTCEPSS rescore
Show 58 more
  1. 2026-09-13 08:20 UTCEG score recompute
  2. 2026-09-11 14:53 UTCEPSS rescore
  3. 2026-09-10 14:39 UTCEG score recompute
  4. 2026-09-10 09:35 UTCEPSS rescore
  5. 2026-09-08 22:01 UTCEPSS rescore
  6. 2026-09-07 20:55 UTCEG score recompute
  7. 2026-09-07 16:01 UTCEPSS rescore
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-04 16:59 UTCEG score recompute
  10. 2026-09-04 05:06 UTCEPSS rescore
  11. 2026-09-02 14:12 UTCEPSS rescore
  12. 2026-09-01 22:53 UTCEG score recompute
  13. 2026-09-01 13:54 UTCEPSS rescore
  14. 2026-08-30 19:17 UTCEPSS rescore
  15. 2026-08-30 01:22 UTCEPSS rescore
  16. 2026-08-29 23:31 UTCEG score recompute
  17. 2026-08-28 21:41 UTCEPSS rescore
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-27 04:43 UTCEG score recompute
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-24 10:57 UTCEG score recompute
  23. 2026-08-23 00:19 UTCEPSS rescore
  24. 2026-08-21 23:49 UTCEPSS rescore
  25. 2026-08-21 17:16 UTCEG score recompute
  26. 2026-08-20 22:55 UTCEPSS rescore
  27. 2026-08-19 17:04 UTCEPSS rescore
  28. 2026-08-18 23:35 UTCEG score recompute
  29. 2026-08-18 13:48 UTCEPSS rescore
  30. 2026-08-17 13:47 UTCEPSS rescore
  31. 2026-08-16 14:56 UTCEPSS rescore
  32. 2026-08-16 05:53 UTCEG score recompute
  33. 2026-08-16 02:14 UTCEPSS rescore
  34. 2026-08-15 01:30 UTCEPSS rescore
  35. 2026-08-13 22:00 UTCEPSS rescore
  36. 2026-08-13 12:12 UTCEG score recompute
  37. 2026-08-12 13:51 UTCEPSS rescore
  38. 2026-08-11 00:00 UTCEPSS rescore
  39. 2026-08-10 18:31 UTCEG score recompute
  40. 2026-08-09 13:46 UTCEPSS rescore
  41. 2026-08-08 16:37 UTCEPSS rescore
  42. 2026-08-08 00:50 UTCEG score recompute
  43. 2026-08-06 13:47 UTCEPSS rescore
  44. 2026-08-05 19:17 UTCEPSS rescore
  45. 2026-08-05 07:10 UTCEG score recompute
  46. 2026-08-04 15:10 UTCEPSS rescore
  47. 2026-08-04 10:39 UTCEPSS rescore
  48. 2026-08-03 10:36 UTCEPSS rescore
  49. 2026-08-02 13:25 UTCEG score recompute
  50. 2026-08-01 04:16 UTCEPSS rescore
  51. 2026-07-30 19:44 UTCEG score recompute
  52. 2026-07-30 16:28 UTCEPSS rescore
  53. 2026-07-30 01:30 UTCEPSS rescore
  54. 2026-07-28 20:26 UTCEG score recompute
  55. 2026-07-28 20:06 UTCEG score recompute
  56. 2026-07-28 17:22 UTCEG score recompute▲ 2.00
  57. 2026-07-28 17:21 UTCNVD updateCVSS v3 → 2 · CVSS v4 → 2
  58. 2026-07-28 16:24 UTCEG score recompute

Related CVEs(same product + same CWE)

Same product

2 shown

Debian:11:ruby-sqlite3 · RubyGems:sqlite3-ruby

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 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.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54619?
CVE-2026-54619 has a CVSS base score of 2.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54619?
A fix for CVE-2026-54619 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54619 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs