CVE-2026-119377

SQLite before 3.54.0 Authorizer Bypass via RIGHT or FULL JOIN USING

Published Oct 30, 2026 CVSS 4.0 · 2 Low EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

SQLite before version 3.54.0 contains a flaw in the lookupName() routine that causes the authorizer function to be invoked only for the first joined table when a RIGHT or FULL JOIN uses a shared USING column. This oversight allows an attacker who can supply arbitrary SQL to read columns that should have been blocked by sqlite3_set_authorizer() SQLITE_READ constraints, thereby bypassing authorization and leaking protected data.

Affected Systems

The vulnerability applies to any SQLite installation that has not been updated to the 3.54.0 release or later, regardless of platform or hosting environment. The CVE record does not enumerate specific affected build identifiers, so all earlier versions are considered vulnerable unless a newer fixed release is in use.

Risk and Exploitability

The CVSS score of 2.0 indicates low severity under the standard metric set, and the EPSS figure of less than 1% signals a very low but non‑zero exploitation probability. The issue is not listed in the CISA KEV catalog, suggesting no known active exploitation. The attack requires the ability to inject or execute crafted SQL statements, typically via a user‑supplied input that is not properly sanitised.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update SQLite to version 3.54.0 or newer.
  • If the database cannot be upgraded immediately, avoid using RIGHT or FULL JOIN statements with USING clauses in contexts that accept untrusted input.
  • Reinforce the sqlite3_set_authorizer() policy to restrict read access more tightly and review application logic to ensure it is not overridden by injected SQL.

Generated by OpenCVE AI on November 6, 2026 at 03:20 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title SQLite before 3.54.0 Authorizer Bypass via RIGHT or FULL JOIN USING
First Time appeared Sqlite
Sqlite sqlite
Weaknesses CWE-863
CPEs cpe:2.3:a:sqlite:sqlite:*:*:*:*:*:*:*:*
Vendors & Products Sqlite
Sqlite sqlite
References
Metrics cvssV3_1

{'score': 2.5, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N'}

cvssV4_0

{'score': 2, 'vector': 'CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-289

    Authentication Bypass by Alternate Name

  • CWE-863

    Incorrect Authorization

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Nov 5, 2026, 9:11 PM
Reserved
Oct 30, 2026, 12:57 AM
Status
Analyzed
Published
Oct 30, 2026, 12:16 PM
Modified
Nov 5, 2026, 10:17 PM
Severity
Low
Public date
Oct 30, 2026, 11:30 AM