<?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>Mon, 04 May 2026 21:36:54 +0000</lastBuildDate>
    <item>
      <title>d4025559-59f5-4ad6-8d2e-2c4207121dd0</title>
      <link>https://vulnerability.circl.lu/sighting/d4025559-59f5-4ad6-8d2e-2c4207121dd0/export</link>
      <description>{"uuid": "d4025559-59f5-4ad6-8d2e-2c4207121dd0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-47551", "type": "seen", "source": "https://t.me/cibsecurity/54944", "content": "\u203c CVE-2022-47551 \u203c\n\nApiman 1.5.7 through 2.2.3.Final has insufficient checks for read permissions within the Apiman Manager REST API. The root cause of the issue is the Apiman project's accidental acceptance of a large contribution that was not fully compatible with the security model of Apiman versions before 3.0.0.Final. Because of this, 3.0.0.Final is not affected by the vulnerability.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-12-20T02:11:56.000000Z"}</description>
      <content:encoded>{"uuid": "d4025559-59f5-4ad6-8d2e-2c4207121dd0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-47551", "type": "seen", "source": "https://t.me/cibsecurity/54944", "content": "\u203c CVE-2022-47551 \u203c\n\nApiman 1.5.7 through 2.2.3.Final has insufficient checks for read permissions within the Apiman Manager REST API. The root cause of the issue is the Apiman project's accidental acceptance of a large contribution that was not fully compatible with the security model of Apiman versions before 3.0.0.Final. Because of this, 3.0.0.Final is not affected by the vulnerability.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-12-20T02:11:56.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/d4025559-59f5-4ad6-8d2e-2c4207121dd0/export</guid>
      <pubDate>Tue, 20 Dec 2022 02:11:56 +0000</pubDate>
    </item>
  </channel>
</rss>
