SQLite before 3.54.0 contains an authorization bypass vulnerability in lookupName() that invokes the authorizer only for the first joined table's USING column. Attackers able to submit SQL can query a shared USING column in a RIGHT or FULL JOIN to read columns denied via sqlite3_set_authorizer() SQLITE_READ restrictions.
Fix
Patch, vendor advisory and mitigation references on NVD 4
- https://sqlite.org/src/info/bbd69ce274620008 patch
- https://github.com/sqlite/sqlite/commit/7ff247c5b9ead3ad8a69c26d3fd264878e127237 patch
- https://sqlite.org/src/info/2cb22877683680c1 patch
- https://github.com/sqlite/sqlite/commit/5694c3bb2a6a40770ecd2f65910eea756734dfd8 patch
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 2.0 · sqliteNVD modified 2026-10-30 11:30
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 10
- https://sqlite.org/bugs/info/2026-07-05T08:15:45Z issue-tracking
- https://sqlite.org/src/info/bbd69ce274620008 patch
- https://github.com/sqlite/sqlite/commit/7ff247c5b9ead3ad8a69c26d3fd264878e127237 patch
- https://sqlite.org/src/info/2cb22877683680c1 patch
- https://github.com/sqlite/sqlite/commit/5694c3bb2a6a40770ecd2f65910eea756734dfd8 patch
- https://github.com/sqlite/sqlite/blob/version-3.53.4/src/resolve.c#L775 technical-description
- https://sqlite.org/releaselog/3_54_0.html release-notes
- https://abraxaslabs.tech/research/sqlite-fj-using-auth third-party-advisory
- https://github.com/sqlite/sqlite product
- https://www.vulncheck.com/advisories/sqlite-before-3.54.0-authorizer-bypass-via-right-or-full-join-using third-party-advisory