https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T23:22:51.391357+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/brew-mailcatcher-cve-2026-54619 BREW-mailcatcher-CVE-2026-54619 — sqlite3-ruby has Use-After-Free When Redefining SQLite Functions with Different Arity 2026-10-03T23:22:51.476384+00:00

Affected: Homebrew: mailcatcher

## Summary

Using `Database#create_function` or `Database#define_function` to define the same function name more than once with different numbers of arguments ("arity") or text encodings will result in a invalid memory read and a segmentation fault.

## Mitigation

Upgrade to sqlite3 gem v2.9.5 or later.

As a workaround, avoid defining multiple custom functions with the same name (varying numbers of arguments or encoding).

## Severity

The sqlite3-ruby maintainers assess this as Low severity. It is reliably triggered after GC when code is structured in a particular way. There is no known general exploit that could be used as a denial of service attack.

 https://cve.radiocsirt.org/vuln/euvd-2026-342207 EUVD-2026-342207 2026-10-03T23:22:51.476446+00:00 EUVD-2026-342207 https://cve.radiocsirt.org/vuln/fkie_cve-2026-54619 fkie_cve-2026-54619 2026-10-03T23:22:51.476463+00:00

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.

 https://cve.radiocsirt.org/vuln/ghsa-28hh-pr2h-2w89 GHSA-28hh-pr2h-2w89 — sqlite3-ruby has Use-After-Free When Redefining SQLite Functions with Different Arity 2026-10-03T23:22:51.476488+00:00

Affected: RubyGems: sqlite3-ruby, RubyGems: sqlite3

## Summary

Using `Database#create_function` or `Database#define_function` to define the same function name more than once with different numbers of arguments ("arity") or text encodings will result in a invalid memory read and a segmentation fault.

## Mitigation

Upgrade to sqlite3 gem v2.9.5 or later.

As a workaround, avoid defining multiple custom functions with the same name (varying numbers of arguments or encoding).

## Severity

The sqlite3-ruby maintainers assess this as Low severity. It is reliably triggered after GC when code is structured in a particular way. There is no known general exploit that could be used as a denial of service attack.

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-54619 UBUNTU-CVE-2026-54619 2026-10-03T23:22:51.476518+00:00

Affected: 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.04:LTS: ruby-sqlite3

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.