EM-20261113-QCAR
VulnerabilityMedium severity
sqlite3-ruby Vulnerability (CVE-2026-128084)
CVE-2026-128084
Status
Developing
Since : signals keep joining.
- First Signal
- Nov 13 18:57 UTCC26 GitHub Advisory Database
- Page Born
- Nov 13 18:57 UTCsecond source joined
- Last Signal
- Nov 13 18:57 UTC2 days before snapshot
- Sources
- 20 official · 2 research, news or crowd
- Open For
- 41 minso far
Life Of This Page
- 1BornA second, independent source names it.
- 2Developing · NowNew signals join; severity can move.
- 3ConfirmedNot yetCISA KEV lists it, or exploitation in the wild is reported.
- 4ResolvedNot yetPast the fix deadline and 14 days with no new signal.
- 5ArchivedNot yet30 days after resolved. Read only; the link keeps working. Reopens if it comes back.
The ID never changes, and earlier addresses keep working. A correction is logged, never overwritten. If two pages turn out to be one incident, the later one points to the earlier.
Vulnerability Lifecycle
- Disclosed: reachedNov 13 18:57 UTCC26 first to name it
- Scored: not yetNot yetNo CVSS yet
- Exploited: not yetNot yetNo exploitation reported
- Advisories: not yetNot yetNone yet
- Vendor Response: not yetNot yetNone in sources yet
- Resolved: not yetNot yetAfter 14 quiet days
Timeline
Point at a mark to read it. Squares are signals, colored by severity; every one is also listed under Signals.
Signals
- GHSA-4fqr-96q8-xrfx / CVE-2026-128084 (opens source in a new tab) sqlite3-ruby: Possible SQL query truncation when a string is 4 GiB or larger Med severityDatabaseC29 CIRCL Vulnerability-Lookup
- GHSA-4fqr-96q8-xrfx / CVE-2026-128084: sqlite3-ruby: Possible SQL query truncation when a string is 4 GiB or larger (opens source in a new tab) rubygems:sqlite3 Med severityDatabaseC26 GitHub Advisory Database