<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 03 Oct 2026 11:55:02 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-33545 — MobSF has SQL Injection in its SQLite Database Viewer Utils</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-33545</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; MobSF Mobile-Security-Framework-MobSF&lt;/p&gt;
&lt;p&gt;MobSF is a mobile application security testing tool used. Prior to version 4.4.6, MobSF&amp;#39;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&amp;#39;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; MobSF Mobile-Security-Framework-MobSF&lt;/p&gt;
&lt;p&gt;MobSF is a mobile application security testing tool used. Prior to version 4.4.6, MobSF&amp;#39;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&amp;#39;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-33545</guid>
    </item>
    <item>
      <title>GHSA-hqjr-43r5-9q58 — MobSF has SQL Injection in its SQLite Database Viewer Utils</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hqjr-43r5-9q58</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: mobsf&lt;/p&gt;
&lt;p&gt;## Description&lt;/p&gt;
&lt;p&gt;MobSF&amp;#39;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&amp;#39;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.&lt;/p&gt;
&lt;p&gt;This allows an attacker to:&lt;/p&gt;
&lt;p&gt;1. **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&amp;#39;s analysis.&lt;/p&gt;
&lt;p&gt;2. **Achieve SQL Injection** -- The `SELECT * FROM` query on line 557 is provably injectable via `UNION SELECT`, allowing attacker-controlled data to be returned in query results. The current code structure (a `PRAGMA` statement that runs first on line 553) limits the full exploitation chain, but the underlying code is verifiably injectable.&lt;/p&gt;
&lt;p&gt;## Root Cause&lt;/p&gt;
&lt;p&gt;The vulnerable code in `mobsf/MobSF/utils.py:542-566`:&lt;/p&gt;
&lt;p&gt;```python
def read_sqlite(sqlite_file):
    &amp;#34;&amp;#34;&amp;#34;Sqlite Dump - Readable Text.&amp;#34;&amp;#34;&amp;#34;
    table_dict = {}
    try:
        con = sqlite3.connect(sqlite_file)
        cur = con.cursor()
        cur.execute(&amp;#39;SELECT name FROM sqlite_master WHERE type=\&amp;#39;table\&amp;#39;;&amp;#39;)
        tables = cur.fetchall()
        for table in tables:…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: mobsf&lt;/p&gt;
&lt;p&gt;## Description&lt;/p&gt;
&lt;p&gt;MobSF&amp;#39;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&amp;#39;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.&lt;/p&gt;
&lt;p&gt;This allows an attacker to:&lt;/p&gt;
&lt;p&gt;1. **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&amp;#39;s analysis.&lt;/p&gt;
&lt;p&gt;2. **Achieve SQL Injection** -- The `SELECT * FROM` query on line 557 is provably injectable via `UNION SELECT`, allowing attacker-controlled data to be returned in query results. The current code structure (a `PRAGMA` statement that runs first on line 553) limits the full exploitation chain, but the underlying code is verifiably injectable.&lt;/p&gt;
&lt;p&gt;## Root Cause&lt;/p&gt;
&lt;p&gt;The vulnerable code in `mobsf/MobSF/utils.py:542-566`:&lt;/p&gt;
&lt;p&gt;```python
def read_sqlite(sqlite_file):
    &amp;#34;&amp;#34;&amp;#34;Sqlite Dump - Readable Text.&amp;#34;&amp;#34;&amp;#34;
    table_dict = {}
    try:
        con = sqlite3.connect(sqlite_file)
        cur = con.cursor()
        cur.execute(&amp;#39;SELECT name FROM sqlite_master WHERE type=\&amp;#39;table\&amp;#39;;&amp;#39;)
        tables = cur.fetchall()
        for table in tables:…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hqjr-43r5-9q58</guid>
    </item>
  </channel>
</rss>
