<?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, 19 Jun 2026 07:10:47 +0000</lastBuildDate>
    <item>
      <title>3bada900-5eab-4ea9-a43e-84d3bfa4995e</title>
      <link>https://vulnerability.circl.lu/sighting/3bada900-5eab-4ea9-a43e-84d3bfa4995e/export</link>
      <description>{"uuid": "3bada900-5eab-4ea9-a43e-84d3bfa4995e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-42798", "type": "seen", "source": "https://t.me/cibsecurity/70952", "content": "\u203c CVE-2023-42798 \u203c\n\nAutomataCI is a template git repository equipped with a native built-in semi-autonomous CI tools. An issue in versions 1.4.1 and below can let a release job reset the git root repository to the first commit. Version 1.5.0 has a patch for this issue. As a workaround, make sure the `PROJECT_PATH_RELEASE` (e.g. `releases/`) directory is manually and actually `git cloned` properly, making it a different git repostiory from the root git repository.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2023-09-22T20:31:54.000000Z"}</description>
      <content:encoded>{"uuid": "3bada900-5eab-4ea9-a43e-84d3bfa4995e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-42798", "type": "seen", "source": "https://t.me/cibsecurity/70952", "content": "\u203c CVE-2023-42798 \u203c\n\nAutomataCI is a template git repository equipped with a native built-in semi-autonomous CI tools. An issue in versions 1.4.1 and below can let a release job reset the git root repository to the first commit. Version 1.5.0 has a patch for this issue. As a workaround, make sure the `PROJECT_PATH_RELEASE` (e.g. `releases/`) directory is manually and actually `git cloned` properly, making it a different git repostiory from the root git repository.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2023-09-22T20:31:54.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/3bada900-5eab-4ea9-a43e-84d3bfa4995e/export</guid>
      <pubDate>Fri, 22 Sep 2023 20:31:54 +0000</pubDate>
    </item>
  </channel>
</rss>
