<?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 sightings.</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent sightings.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 24 Jul 2026 15:26:32 +0000</lastBuildDate>
    <item>
      <title>4ddf2047-60d8-4620-9071-1d11ec76c5e3</title>
      <link>https://vulnerability.circl.lu/sighting/4ddf2047-60d8-4620-9071-1d11ec76c5e3/export</link>
      <description>{"uuid": "4ddf2047-60d8-4620-9071-1d11ec76c5e3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-8985", "type": "seen", "source": "https://bsky.app/profile/stackflag.bsky.social/post/3mratv7bbrw2e", "content": "CVE-2026-8985 - maxicharger single\nThe Autel Maxi Charger Single firmware is vulnerable to unauthorized code execution through the /test endpoint on TCP port 9002. This means an attacker can send\u2026\n\nToo many irrelevant or confusing CVEs? Use stackflag.com\n\n#maxichargersingle #autel #CVE #infosec", "creation_timestamp": "2026-07-22T17:28:05.941961Z"}</description>
      <content:encoded>{"uuid": "4ddf2047-60d8-4620-9071-1d11ec76c5e3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-8985", "type": "seen", "source": "https://bsky.app/profile/stackflag.bsky.social/post/3mratv7bbrw2e", "content": "CVE-2026-8985 - maxicharger single\nThe Autel Maxi Charger Single firmware is vulnerable to unauthorized code execution through the /test endpoint on TCP port 9002. This means an attacker can send\u2026\n\nToo many irrelevant or confusing CVEs? Use stackflag.com\n\n#maxichargersingle #autel #CVE #infosec", "creation_timestamp": "2026-07-22T17:28:05.941961Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/4ddf2047-60d8-4620-9071-1d11ec76c5e3/export</guid>
      <pubDate>Wed, 22 Jul 2026 17:28:05 +0000</pubDate>
    </item>
    <item>
      <title>65b0f2a4-cb19-4305-90da-051a7bd577e2</title>
      <link>https://vulnerability.circl.lu/sighting/65b0f2a4-cb19-4305-90da-051a7bd577e2/export</link>
      <description>{"uuid": "65b0f2a4-cb19-4305-90da-051a7bd577e2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-8985", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3mr7a3gina72s", "content": "CVE-2026-8985 - Unauthenticated Command Injection\nCVE ID : CVE-2026-8985\n \n Published : July 21, 2026, 10:19 p.m. | 2\u00a0hours, 17\u00a0minutes ago\n \n Description : Autel Maxi Charger Single firmware through V1.03.51 is vulnerable to OS command injection in the /test endpoint exposed ...", "creation_timestamp": "2026-07-22T02:01:00.642097Z"}</description>
      <content:encoded>{"uuid": "65b0f2a4-cb19-4305-90da-051a7bd577e2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-8985", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3mr7a3gina72s", "content": "CVE-2026-8985 - Unauthenticated Command Injection\nCVE ID : CVE-2026-8985\n \n Published : July 21, 2026, 10:19 p.m. | 2\u00a0hours, 17\u00a0minutes ago\n \n Description : Autel Maxi Charger Single firmware through V1.03.51 is vulnerable to OS command injection in the /test endpoint exposed ...", "creation_timestamp": "2026-07-22T02:01:00.642097Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/65b0f2a4-cb19-4305-90da-051a7bd577e2/export</guid>
      <pubDate>Wed, 22 Jul 2026 02:01:00 +0000</pubDate>
    </item>
  </channel>
</rss>
