CVE-2026-119377 SQLite before 3.54.0 Authorizer Bypass via RIGHT or FULL JOIN USING
Low 2.0
Published
Updated
Check this codebase for CVE-2026-119377 and fix it if it is affected.
What it is: CVE-2026-119377 is a low-severity vulnerability in SQLite, published on 30 Oct 2026.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119377 exists.
Affected product: SQLite. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-119377/ (Markdown: https://insights.sbomify.com/CVE-2026-119377/index.md)
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2026-119377?
CVE-2026-119377 is a low-severity vulnerability in SQLite, published on 30 Oct 2026.
Official 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.
Weakness: CWE-863
Which versions are affected by CVE-2026-119377?
It affects 1 product.
Products include SQLite.
How do I fix CVE-2026-119377?
Upgrade to a fixed version.
Is CVE-2026-119377 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119377 exists.
Other vulnerabilities in SQLite
- CVE-2015-5895 Multiple unspecified vulnerabilities in SQLite before 3.8.10.2, as used in Apple iOS before 9, have unknown impact and attack vectors.
- CVE-2020-35527 In SQLite 3.31.1, there is an out of bounds access problem through ALTER TABLE for views that have a nested FROM clause.
- CVE-2019-8457 SQLite3 from 3.6.0 to and including 3.27.2 is vulnerable to heap out-of-bound read in the rtreenode() function when handling invalid rtree tables.
- CVE-2017-10989 The getNodeSize function in ext/rtree/rtree.c in SQLite through 3.19.3, as used in GDAL and other products, mishandles undersized RTree blob
- CVE-2026-119373 SQLite before 3.54.0 FTS5 Heap Buffer Overflow via fts5MergeRowidLists()
Sources
Also known as AZL-111781, DEBIAN-CVE-2026-119377, ECHO-ffd2-f399-3d1f, GHSA-qqg5-vxjp-68gf, UBUNTU-CVE-2026-119377.