Repository navigation
chore(audit): ignore RUSTSEC-2026-0459 until sqlx allows libsqlite3-sys 0.39 - #74
Merged
Merged
Conversation
…ys 0.39 The fix needs libsqlite3-sys >= 0.39, but sqlx-sqlite 0.9.0 caps it below 0.38 and no newer sqlx is released. Exposure is limited to a crafted database plus -wal pair in a path the user controls. Rationale and the removal trigger are in .cargo/audit.toml. Refs #72
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Refs #72.
cargo auditfails on RUSTSEC-2026-0459 (CVE-2026-119375): bundled SQLite before 3.54.0 can leak uninitialized page-cache memory when it opens a database with a crafted-walfile.Why no upgrade: the fix is libsqlite3-sys >= 0.39. The chain is sea-orm 2.0 -> sqlx 0.9.0 -> sqlx-sqlite 0.9.0, which requires
libsqlite3-sys >=0.30.1, <0.38.0. 0.9.0 is the latest sqlx release. sqlxmainalready widens this to<0.40.0, so the next release unblocks it.Why the ignore is acceptable for now: the code is compiled in (
bundled), but exploiting it needs an attacker who can already write both~/.bbmctl/measurements.db(or the user-supplied path) and its-walfile. Local only, user interaction required, read-only impact.The full rationale and the removal trigger are documented in
.cargo/audit.toml, matching the two existing entries. #72 stays open until the ignore is removed.