SQL Injection in mobsf (CVE-2026-33545)
Summary
SQL injection in mobsf (CVE-2026-33545). Risk of unauthorized operations or information disclosure. Exploitable via sqlite_master. Mitigation: upgrade to 4.4.6 or later.
Original description
The description as published by the source.
Description
MobSF's read_sqlite() function in mobsf/MobSF/utils.py (lines 542-566) uses Python string formatting (%) to construct SQL queries with table names read from a SQLite database's sqlite_master table. When a security analyst uses MobSF to analyze a malicious mobile application containing a crafted SQLite database, attacker-controlled table names are interpolated directly into SQL queries without parameterization or escaping.
This allows an attacker to:
-
Cause Denial of Service -- A malicious table name causes the database viewer to crash, preventing the analyst from viewing ANY data in the SQLite database. A malicious app can use this to hide sensitive data (C2 server URLs, stolen credentials, API keys) from MobSF's analysis.
-
Achieve SQL Injection -- The
SELECT * FROMquery on line 557 is provably injectable viaUNION SELECT, allowing attacker-controlled data to be returned in query results. The current code structure (aPRAGMAstatement that runs first on line 553) limits the full exploitation chain, but the underlying code is verifiably injectable.
Root Cause
The vulnerable code in mobsf/MobSF/utils.py:542-566:
def read_sqlite(sqlite_file):
"""Sqlite Dump - Readable Text."""
table_dict = {}
try:
con = sqlite3.connect(sqlite_file)
cur = con.cursor()
cur.execute('SELECT name FROM sqlite_master WHERE type=\'table\';')
tables = cur.fetchall()
for table in tables:…
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-33545 has been found in mobsf.
Attackers can target a specific entry point like sqlite_master over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade mobsf to 4.4.6 or later.
If unsure, ask your IT team or search "mobsf CVE-2026-33545" on the vendor's site.
CVE-2026-33545 (mobsf) — CWE-89
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: sqlite_master / PRAGMA / table / sqlite3.OperationalError
Patched: 4.4.6 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SQL injection (CWE-89) exists in mobsf. Attackers reach the vulnerable code path via sqlite_master without authentication.
Check the vendor advisory for the affected versions of mobsf. Attack surface: sqlite_master / PRAGMA / table / sqlite3.OperationalError.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 4.4.6.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'mobsf' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'mobsf' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
mobsfを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade mobsf to 4.4.6ステージング環境で 4.4.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com