# CVE-2026-33545: MobSF has SQL Injection in its SQLite Database Viewer Utils

> An attacker can execute arbitrary SQL commands and cause denial of service by providing a malicious mobile app with a crafted SQLite database to MobSF.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 26 Mar 2026
- **Updated:** 27 Mar 2026
- **Also known as:** GHSA-hqjr-43r5-9q58, PYSEC-2026-2662

## What is CVE-2026-33545?

CVE-2026-33545 is a medium-severity SQL injection vulnerability in Mobile-Security-Framework-MobSF, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

MobSF is a mobile application security testing tool used. Prior to version 4.4.6, 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 and achieve SQL injection. Version 4.4.6 patches the issue.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-33545?

3 open source packages ship an affected version, including mobsf. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mobsf` | PyPI | All versions | 4.4.6 |
| `mobsf` | PyPI | All versions | 4.4.6 |
| `mobsf` | PyPI | All versions | 4.4.6 |

Products: Opensecurity Mobile Security Framework.

## How do I fix CVE-2026-33545?

Upgrade mobsf to 4.4.6 or later.

## Is CVE-2026-33545 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33545 exists.

## Other vulnerabilities in Mobile-Security-Framework-MobSF

- [CVE-2025-46335](https://insights.sbomify.com/CVE-2025-46335/): Mobile Security Framework (MobSF) Allows Stored Cross Site Scripting (XSS) via malicious SVG Icon Upload (high 8.6)
- [CVE-2025-24805](https://insights.sbomify.com/CVE-2025-24805/): Local Privilege Escalation in MobSF (high 8.5)
- [CVE-2025-24803](https://insights.sbomify.com/CVE-2025-24803/): Stored Cross-Site Scripting (XSS) in MobSF (high 8.4)
- [CVE-2026-24490](https://insights.sbomify.com/CVE-2026-24490/): MobSF has Stored XSS via Manifest Analysis - Dialer Code Host Field (high 8.1)
- [CVE-2024-53999](https://insights.sbomify.com/CVE-2024-53999/): Mobile Security Framework (MobSF) Stored Cross-Site Scripting Vulnerability in "Diff or Compare" Functionality (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33545 and fix it if it is affected.

What it is: CVE-2026-33545 is a medium-severity SQL injection vulnerability in Mobile-Security-Framework-MobSF, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33545 exists.

Affected packages and fixed versions:
- mobsf (PyPI): affected all versions; fixed in 4.4.6
- mobsf (PyPI): affected all versions; fixed in 4.4.6
- mobsf (PyPI): affected all versions; fixed in 4.4.6

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-33545/ (Markdown: https://insights.sbomify.com/CVE-2026-33545/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33545
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33545
- OSV: https://osv.dev/vulnerability/CVE-2026-33545

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33545/
Summaries are generated and may contain mistakes; the official description above is the record.