<?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://vulnerability.circl.lu/sightings/feed</id>
  <title>Most recent sightings.</title>
  <updated>2026-09-13T05:56:45.443337+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent sightings.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/sighting/467ea923-f892-46ae-aad9-a0df37f69e51/export</id>
    <title>467ea923-f892-46ae-aad9-a0df37f69e51</title>
    <updated>2026-09-13T05:56:45.469949+00:00</updated>
    <author>
      <name>Automation user</name>
      <uri>https://cve.circl.lu/user/automation</uri>
    </author>
    <content>{"uuid": "467ea923-f892-46ae-aad9-a0df37f69e51", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2026-85620", "type": "seen", "source": "https://bsky.app/profile/getpacketai.bsky.social/post/3mv5s6ryhlx25", "content": "When your AI-to-database safety layer relies on a custom SQL parser that doesn't perfectly match Postgres's quirks, you've got a\u2026\n\nhttps://dev.to/coridev/cve-2026-85620-when-your-mcp-servers-allowlist-parser-isnt-the-one-actually-parsing-sql-13de\n\n#DevOps #platform", "creation_timestamp": "2026-09-10T10:00:27.520986Z"}</content>
    <link href="https://vulnerability.circl.lu/sighting/467ea923-f892-46ae-aad9-a0df37f69e51/export"/>
    <published>2026-09-10T10:00:27.520986+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/sighting/5b9add00-2e30-4ced-9bc8-df376f726751/export</id>
    <title>5b9add00-2e30-4ced-9bc8-df376f726751</title>
    <updated>2026-09-13T05:56:45.472291+00:00</updated>
    <author>
      <name>Automation user</name>
      <uri>https://cve.circl.lu/user/automation</uri>
    </author>
    <content>{"uuid": "5b9add00-2e30-4ced-9bc8-df376f726751", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-85620", "type": "seen", "source": "https://bsky.app/profile/hermes71.bsky.social/post/3muvq3xevju2u", "content": "Daily IT Security Digest \u2014 2026-09-07\nalready added it to the KEV catalogue. This is part of a broader Microsoft vulnerability avalanche covering Entra, Azure, and Copilot. All Chrome and Edge users should update immediately.\n\n## 5. Postgres MCP Restricted-Mode Bypass (CVE-2026-85620)\n\nPostgres MCP", "creation_timestamp": "2026-09-07T05:01:47.235924Z"}</content>
    <link href="https://vulnerability.circl.lu/sighting/5b9add00-2e30-4ced-9bc8-df376f726751/export"/>
    <published>2026-09-07T05:01:47.235924+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/sighting/e24af9a8-846b-4e3e-8df3-765d105e3d0e/export</id>
    <title>e24af9a8-846b-4e3e-8df3-765d105e3d0e</title>
    <updated>2026-09-13T05:56:45.472537+00:00</updated>
    <author>
      <name>Automation user</name>
      <uri>https://cve.circl.lu/user/automation</uri>
    </author>
    <content>{"uuid": "e24af9a8-846b-4e3e-8df3-765d105e3d0e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-85620", "type": "seen", "source": "https://bsky.app/profile/stemshop.bsky.social/post/3mupdvj7gah25", "content": "\ud83d\udea8 CVE-2026-85620 \u2014 CVSS 9.2 CRITICAL\n\nPostgres MCP Pro 0.3.0 contains a restricted-mode bypass vulnerability where function-name validation is no...\n\n\ud83d\udd0e https://stemshop.top/cve/CVE-2026-85620\n\n#CVE #CyberSecurity #InfoSec", "creation_timestamp": "2026-09-04T16:07:30.184502Z"}</content>
    <link href="https://vulnerability.circl.lu/sighting/e24af9a8-846b-4e3e-8df3-765d105e3d0e/export"/>
    <published>2026-09-04T16:07:30.184502+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/sighting/da4515a3-d97f-4c42-8b0b-1f6084e67bd7/export</id>
    <title>da4515a3-d97f-4c42-8b0b-1f6084e67bd7</title>
    <updated>2026-09-13T05:56:45.472737+00:00</updated>
    <author>
      <name>Automation user</name>
      <uri>https://cve.circl.lu/user/automation</uri>
    </author>
    <content>{"uuid": "da4515a3-d97f-4c42-8b0b-1f6084e67bd7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-85620", "type": "seen", "source": "https://bsky.app/profile/stackflag.bsky.social/post/3mupdidgp2l2d", "content": "CVE-2026-85620 - postgres-mcp\nThe Postgres MCP Pro version 0.3.0 can be tricked into running file\u2011reading commands even when restricted mode is turned on. An attacker could use a special query to make\u2026\n\nToo many irrelevant or confusing CVEs? Use stackflag.com\n\n#postgresmcp #crystaldba #CVE #infosec", "creation_timestamp": "2026-09-04T16:00:05.379535Z"}</content>
    <link href="https://vulnerability.circl.lu/sighting/da4515a3-d97f-4c42-8b0b-1f6084e67bd7/export"/>
    <published>2026-09-04T16:00:05.379535+00:00</published>
  </entry>
</feed>
