<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T23:59:26.582517+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/cve-2025-62800</id>
    <title>CVE-2025-62800 — FastMCP vulnerable to reflected XSS in client's callback page</title>
    <updated>2026-09-30T23:59:26.585885+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> jlowin fastmcp</p>
<p>FastMCP is the standard framework for building MCP applications. Versions prior to 2.13.0 have a reflected cross-site scripting vulnerability in the OAuth client callback page (oauth_callback.py) where unescaped user-controlled values are inserted into the generated HTML, allowing arbitrary JavaScript execution in the callback server origin. The issue is fixed in version 2.13.0.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2025-62800"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-mxxr-jv3v-6pgc</id>
    <title>GHSA-mxxr-jv3v-6pgc — FastMCP vulnerable to reflected XSS in client's callback page</title>
    <updated>2026-09-30T23:59:26.585979+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: fastmcp</p>
<p>### Summary
While setting up an oauth client, it was noticed that the callback page hosted by the client during the flow embeds user-controlled content without escaping or sanitizing it. This leads to a reflected Cross-Site-Scripting vulnerability.</p>
<p>### Details
The affected code is located in *https://github.com/jlowin/fastmcp/blob/main/src/fastmcp/client/oauth_callback.py*, which embeds all values passed to the `create_callback_html` function via the `message` parameter it into the callback page without escaping them. This can, for example, be abused by calling the callback server with an XSS payload inside the `error` GET parameter, the value of which will then be inserted into the callback page, causing the execution of attacker-controlled JavaScript code in the callback server's origin. Note that besides the `error` parameter, other parameters reaching this function are affected too.</p>
<p>### PoC
1. Setup a simple fastmcp client such as this one (the callback server's port was fixated for simplicity):</p>
<p>```
url="http://127.0.0.1:8000/mcp"
oauth = OAuth(mcp_url=url,callback_port=1337)</p>
<p>async def main():
    async with Client(url, auth=oauth) as client:
        await client.ping()
        
        # List available operations
        tools = await client.list_tools()</p>
<p>print(f"tools: {tools}")
       
asyncio.run(main())
```</p>
<p>2. Ensure that the MCP server located at `http://127.0.0.1:8000/mcp` supports oauth.
3. Start the client.
4. As soon as the callback server has been…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-mxxr-jv3v-6pgc"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/pysec-2026-1364</id>
    <title>PYSEC-2026-1364 — FastMCP vulnerable to reflected XSS in client's callback page</title>
    <updated>2026-09-30T23:59:26.586067+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: fastmcp</p>
<p>### Summary
While setting up an oauth client, it was noticed that the callback page hosted by the client during the flow embeds user-controlled content without escaping or sanitizing it. This leads to a reflected Cross-Site-Scripting vulnerability.</p>
<p>### Details
The affected code is located in *https://github.com/jlowin/fastmcp/blob/main/src/fastmcp/client/oauth_callback.py*, which embeds all values passed to the `create_callback_html` function via the `message` parameter it into the callback page without escaping them. This can, for example, be abused by calling the callback server with an XSS payload inside the `error` GET parameter, the value of which will then be inserted into the callback page, causing the execution of attacker-controlled JavaScript code in the callback server's origin. Note that besides the `error` parameter, other parameters reaching this function are affected too.</p>
<p>### PoC
1. Setup a simple fastmcp client such as this one (the callback server's port was fixated for simplicity):</p>
<p>```
url="http://127.0.0.1:8000/mcp"
oauth = OAuth(mcp_url=url,callback_port=1337)</p>
<p>async def main():
    async with Client(url, auth=oauth) as client:
        await client.ping()
        
        # List available operations
        tools = await client.list_tools()</p>
<p>print(f"tools: {tools}")
       
asyncio.run(main())
```</p>
<p>2. Ensure that the MCP server located at `http://127.0.0.1:8000/mcp` supports oauth.
3. Start the client.
4. As soon as the callback server has been…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/pysec-2026-1364"/>
  </entry>
</feed>
