<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-22T16:11:07.787315+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-408865</id>
    <title>EUVD-2026-408865</title>
    <updated>2026-11-22T16:11:07.789375+00:00</updated>
    <content>EUVD-2026-408865</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-408865"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-130008</id>
    <title>fkie_cve-2026-130008</title>
    <updated>2026-11-22T16:11:07.789406+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>sqlite-mcp is a Model Context Protocol server for SQLite. Prior to 0.1.2, the default read-only mode can be bypassed through execute_query, which accepts a leading SELECT while the SQLite driver executes trailing statements, and through describe_table, which interpolates the caller-controlled table_name into PRAGMA table_info. Either path can issue ATTACH DATABASE, which opens an attached file read-write despite mode=ro and can make the protected database writable, read other SQLite database files, or create a SQLite-format file at a path writable by the server process. Existing non-empty files that are not SQLite databases are refused and left unchanged. The server has no built-in authentication and listens on all interfaces at :8080 by default, so any client that can reach the port can invoke these tools unless an authenticating proxy is in place. This issue is fixed in version 0.1.2.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-130008"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-q433-mp6c-8v4f</id>
    <title>GHSA-q433-mp6c-8v4f — sqlite-mcp: Read-only mode bypass via statement chaining and SQL injection in describe_table</title>
    <updated>2026-11-22T16:11:07.789440+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/StacklokLabs/sqlite-mcp</p>
<p>### Summary</p>
<p>In read-only mode (the default), a client that can call the MCP tools can write to the database the server is meant to expose read-only, read other SQLite files, and create new SQLite files anywhere the server process can write. There are two ways in: statement chaining through `execute_query`, and SQL injection through `describe_table`.</p>
<p>### Details</p>
<p>- **Statement chaining in `execute_query`.** The only check was that the query starts with `SELECT`. The `modernc.org/sqlite` driver runs every `;`-separated statement in one call, so anything after `SELECT 1;` ran unchecked.
- **SQL injection in `describe_table`.** The `table_name` argument was interpolated into `PRAGMA table_info(%s)` with no guard.
- **Escaping read-only mode.** Through either path, `ATTACH DATABASE` opens a file read-write regardless of the main connection's `mode=ro`. Attaching the protected database itself made it writable. Attaching another path read that file, or created it if it did not exist.</p>
<p>Read-write mode is not affected beyond its intended capabilities, apart from `ATTACH` reaching files other than the configured database.</p>
<p>### Impact</p>
<p>- Modify the database that read-only mode is meant to protect.
- Read any SQLite database file the server process can read.
- Create new SQLite-format files anywhere the server process can write, or write to existing SQLite or empty files. Existing non-empty files that are not SQLite databases are refused and left unchanged.</p>
<p>The server has no built-in…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-q433-mp6c-8v4f"/>
  </entry>
</feed>
