Hi SRMs,

[ Reason ]
There are two low priority security issues in sqlite3, both have the
same root cause. The fix for these is easy.

[ Impact ]
Users will be safe from these attacks, which may compromise their systems.

[ Tests ]
Build and some basic testing.

[ Risks ]
Very small as the change is small and quite straight forward. Only
correct the check.

[ Checklist ]
[x] *all* changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in stable
[x] the issues are verified as fixed in unstable

Thanks,
Laszlo/GCS

Hi,

Please go ahead.

Thanks,

package release.debian.org
tags 1141424 = trixie pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian trixie.

Thanks for your contribution!

Upload details
==============

Package: sqlite3
Version: 3.46.1-7+deb13u2

Explanation: fix FTS5 handling of corrupt records [CVE-2026-11822 CVE-2026-11824]

package release.debian.org
tags 1141424 = trixie pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian trixie.

Thanks for your contribution!

Upload details
==============

Package: sqlite3
Version: 3.46.1-7+deb13u2

Explanation: fix FTS5 handling of corrupt records [CVE-2026-11822 CVE-2026-11824]