<?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>Sat, 06 Jun 2026 13:20:10 +0000</lastBuildDate>
    <item>
      <title>fc29cdc0-50f8-4cd5-bf17-392c34ffcec5</title>
      <link>https://vulnerability.circl.lu/sighting/fc29cdc0-50f8-4cd5-bf17-392c34ffcec5/export</link>
      <description>{"uuid": "fc29cdc0-50f8-4cd5-bf17-392c34ffcec5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-36815", "type": "seen", "source": "https://t.me/cibsecurity/38223", "content": "\u203c CVE-2021-36815 \u203c\n\n** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues during 2021. Notes: none.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-03-01T02:28:45.000000Z"}</description>
      <content:encoded>{"uuid": "fc29cdc0-50f8-4cd5-bf17-392c34ffcec5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-36815", "type": "seen", "source": "https://t.me/cibsecurity/38223", "content": "\u203c CVE-2021-36815 \u203c\n\n** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues during 2021. Notes: none.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-03-01T02:28:45.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/fc29cdc0-50f8-4cd5-bf17-392c34ffcec5/export</guid>
      <pubDate>Tue, 01 Mar 2022 02:28:45 +0000</pubDate>
    </item>
    <item>
      <title>3fb4571c-b2ca-4c37-8453-7127da5b57d1</title>
      <link>https://vulnerability.circl.lu/sighting/3fb4571c-b2ca-4c37-8453-7127da5b57d1/export</link>
      <description>{"uuid": "3fb4571c-b2ca-4c37-8453-7127da5b57d1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-3681", "type": "seen", "source": "https://t.me/cibsecurity/41048", "content": "\u203c CVE-2021-3681 \u203c\n\nA flaw was found in Ansible Galaxy Collections. When collections are built manually, any files in the repository directory that are not explicitly excluded via the ``build_ignore`` list in \"galaxy.yml\" include files in the ``.tar.gz`` file. This contains sensitive info, such as the user's Ansible Galaxy API key and any secrets in ``ansible`` or ``ansible-playbook`` verbose output without the``no_log`` redaction. Currently, there is no way to deprecate a Collection Or delete a Collection Version. Once published, anyone who downloads or installs the collection can view the secrets.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-04-18T20:29:49.000000Z"}</description>
      <content:encoded>{"uuid": "3fb4571c-b2ca-4c37-8453-7127da5b57d1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-3681", "type": "seen", "source": "https://t.me/cibsecurity/41048", "content": "\u203c CVE-2021-3681 \u203c\n\nA flaw was found in Ansible Galaxy Collections. When collections are built manually, any files in the repository directory that are not explicitly excluded via the ``build_ignore`` list in \"galaxy.yml\" include files in the ``.tar.gz`` file. This contains sensitive info, such as the user's Ansible Galaxy API key and any secrets in ``ansible`` or ``ansible-playbook`` verbose output without the``no_log`` redaction. Currently, there is no way to deprecate a Collection Or delete a Collection Version. Once published, anyone who downloads or installs the collection can view the secrets.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-04-18T20:29:49.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/3fb4571c-b2ca-4c37-8453-7127da5b57d1/export</guid>
      <pubDate>Mon, 18 Apr 2022 20:29:49 +0000</pubDate>
    </item>
  </channel>
</rss>
