<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 17 Nov 2026 03:34:10 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-406505</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-406505</link>
      <description>EUVD-2026-406505</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-406505</guid>
    </item>
    <item>
      <title>GHSA-4fqr-96q8-xrfx — sqlite3-ruby: Possible SQL query truncation when a string is 4 GiB or larger</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4fqr-96q8-xrfx</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: sqlite3&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;sqlite3-ruby cast Ruby string lengths (`long`) to `int` before passing them to SQLite. On 64-bit platforms, a string of 4 GiB (2^32 bytes) or larger had its length wrap, so SQLite saw only the first `length mod 2^32` bytes. An attacker who controls the length of a SQL string could truncate the query, for example dropping a trailing `WHERE` clause. The affected paths are:&lt;/p&gt;
&lt;p&gt;- the SQL passed to `Database#prepare`, `#execute`, and related methods
- String and Blob values passed to `Statement#bind_param` and related methods
- String and Blob values returned from SQL functions and aggregates defined in Ruby (`Database#create_function`, `#create_aggregate`, and related methods)&lt;/p&gt;
&lt;p&gt;sqlite3 v2.10.2 raises `RangeError` when any of these strings is longer than `INT_MAX` bytes.&lt;/p&gt;
&lt;p&gt;### Severity&lt;/p&gt;
&lt;p&gt;The sqlite3-ruby maintainers have evaluated this as medium severity (CVSS 4.8). Exploitation requires an attacker to get at least 4 GiB into a single SQL string or bound value. Most deployments reject a request body that large before the application sees it, and the server must hold several copies of the string in memory.&lt;/p&gt;
&lt;p&gt;A truncated bound value is only a prefix of the attacker&amp;#39;s input, so the bind paths matter only where the application validated the full value. A truncated SQL string is more serious: when the attacker&amp;#39;s input is inlined into the SQL, the clauses that follow it are dropped. If a dropped clause contained a bind placeholder, binding raises `SQLite3::RangeException` inste…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: sqlite3&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;sqlite3-ruby cast Ruby string lengths (`long`) to `int` before passing them to SQLite. On 64-bit platforms, a string of 4 GiB (2^32 bytes) or larger had its length wrap, so SQLite saw only the first `length mod 2^32` bytes. An attacker who controls the length of a SQL string could truncate the query, for example dropping a trailing `WHERE` clause. The affected paths are:&lt;/p&gt;
&lt;p&gt;- the SQL passed to `Database#prepare`, `#execute`, and related methods
- String and Blob values passed to `Statement#bind_param` and related methods
- String and Blob values returned from SQL functions and aggregates defined in Ruby (`Database#create_function`, `#create_aggregate`, and related methods)&lt;/p&gt;
&lt;p&gt;sqlite3 v2.10.2 raises `RangeError` when any of these strings is longer than `INT_MAX` bytes.&lt;/p&gt;
&lt;p&gt;### Severity&lt;/p&gt;
&lt;p&gt;The sqlite3-ruby maintainers have evaluated this as medium severity (CVSS 4.8). Exploitation requires an attacker to get at least 4 GiB into a single SQL string or bound value. Most deployments reject a request body that large before the application sees it, and the server must hold several copies of the string in memory.&lt;/p&gt;
&lt;p&gt;A truncated bound value is only a prefix of the attacker&amp;#39;s input, so the bind paths matter only where the application validated the full value. A truncated SQL string is more serious: when the attacker&amp;#39;s input is inlined into the SQL, the clauses that follow it are dropped. If a dropped clause contained a bind placeholder, binding raises `SQLite3::RangeException` inste…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-4fqr-96q8-xrfx</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-128084</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-128084</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: ruby-sqlite3, Ubuntu:18.04:LTS: ruby-sqlite3, Ubuntu:20.04:LTS: ruby-sqlite3, Ubuntu:22.04:LTS: ruby-sqlite3, Ubuntu:24.04:LTS: ruby-sqlite3, Ubuntu:26.10: ruby-sqlite3, Ubuntu:26.04:LTS: ruby-sqlite3&lt;/p&gt;
&lt;p&gt;sqlite3 provides Ruby bindings for the SQLite3 embedded database. Prior to 2.10.2, sqlite3-ruby casts Ruby string lengths to int before passing SQL through Database#prepare, bound String or Blob values through Statement#bind_param, and String or Blob results from Ruby-defined SQL functions and aggregates through Database#create_function and Database#create_aggregate. On 64-bit platforms, a string of 4 GiB (2^32 bytes) or larger can wrap the length so SQLite processes only a prefix. A truncated SQL string can drop trailing clauses such as a WHERE condition, while a truncated bound value matters only when the application validated the full value before binding it. Exploitation requires the application and server to accept and retain the unusually large attacker-controlled string. If a dropped SQL clause contained a bind placeholder, binding raises SQLite3::RangeException instead of running the query. This issue is fixed in version 2.10.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: ruby-sqlite3, Ubuntu:18.04:LTS: ruby-sqlite3, Ubuntu:20.04:LTS: ruby-sqlite3, Ubuntu:22.04:LTS: ruby-sqlite3, Ubuntu:24.04:LTS: ruby-sqlite3, Ubuntu:26.10: ruby-sqlite3, Ubuntu:26.04:LTS: ruby-sqlite3&lt;/p&gt;
&lt;p&gt;sqlite3 provides Ruby bindings for the SQLite3 embedded database. Prior to 2.10.2, sqlite3-ruby casts Ruby string lengths to int before passing SQL through Database#prepare, bound String or Blob values through Statement#bind_param, and String or Blob results from Ruby-defined SQL functions and aggregates through Database#create_function and Database#create_aggregate. On 64-bit platforms, a string of 4 GiB (2^32 bytes) or larger can wrap the length so SQLite processes only a prefix. A truncated SQL string can drop trailing clauses such as a WHERE condition, while a truncated bound value matters only when the application validated the full value before binding it. Exploitation requires the application and server to accept and retain the unusually large attacker-controlled string. If a dropped SQL clause contained a bind placeholder, binding raises SQLite3::RangeException instead of running the query. This issue is fixed in version 2.10.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-128084</guid>
    </item>
  </channel>
</rss>
