<?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>Tue, 06 Oct 2026 14:52:35 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-48529 — GitHub MCP Server: Lockdown mode singleton in HTTP server causes cross-user GraphQL client confusion</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-48529</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; github-mcp-server&lt;/p&gt;
&lt;p&gt;GitHub MCP Server is GitHub&amp;#39;s official MCP Server. From 0.22.0 until 1.1.2, when running in HTTP mode with --lockdown-mode enabled, the RepoAccessCache is implemented as a process-global singleton initialized with the first authenticated user&amp;#39;s GraphQL client. All subsequent requests from different users share this singleton and their lockdown-related GraphQL queries are executed using the first user&amp;#39;s credentials. The singleton is never updated to reflect later users&amp;#39; tokens. This vulnerability is fixed in 1.1.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; github-mcp-server&lt;/p&gt;
&lt;p&gt;GitHub MCP Server is GitHub&amp;#39;s official MCP Server. From 0.22.0 until 1.1.2, when running in HTTP mode with --lockdown-mode enabled, the RepoAccessCache is implemented as a process-global singleton initialized with the first authenticated user&amp;#39;s GraphQL client. All subsequent requests from different users share this singleton and their lockdown-related GraphQL queries are executed using the first user&amp;#39;s credentials. The singleton is never updated to reflect later users&amp;#39; tokens. This vulnerability is fixed in 1.1.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-48529</guid>
    </item>
  </channel>
</rss>
