CVE-2026-119377EUVD-2026-113788GHSA-QQG5-VXJP-68GF
SQLite before 3.54.0 Authorizer Bypass via RIGHT or FULL JOIN USING
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.54.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
SQLite, a widely used embedded database library, is affected before version 3.54.0 (version numbers omitted here). An attacker who can submit SQL queries could use a RIGHT or FULL JOIN with a shared USING column to read data from columns that the application's authorizer has explicitly blocked, bypassing access restrictions.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- SQLite SQLite
fixed in 3.54.0