<?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://db.gcve.eu</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 03:14:29 +0000</lastBuildDate>
    <item>
      <title>b32639c9-1f36-435b-a44d-1e3b389231ee</title>
      <link>https://db.gcve.eu/sighting/b32639c9-1f36-435b-a44d-1e3b389231ee/export</link>
      <description>{"uuid": "b32639c9-1f36-435b-a44d-1e3b389231ee", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2022-31055", "type": "seen", "source": "https://t.me/cibsecurity/44319", "content": "\u203c CVE-2022-31055 \u203c\n\nkCTF is a Kubernetes-based infrastructure for capture the flag (CTF) competitions. Prior to version 1.6.0, the kctf cluster set-src-ip-ranges was broken and allowed traffic from any IP. The problem has been patched in v1.6.0. As a workaround, those who want to test challenges privately can mark them as `public: false` and use `kctf chal debug port-forward` to connect.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-06-13T20:17:12.000000Z"}</description>
      <content:encoded>{"uuid": "b32639c9-1f36-435b-a44d-1e3b389231ee", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2022-31055", "type": "seen", "source": "https://t.me/cibsecurity/44319", "content": "\u203c CVE-2022-31055 \u203c\n\nkCTF is a Kubernetes-based infrastructure for capture the flag (CTF) competitions. Prior to version 1.6.0, the kctf cluster set-src-ip-ranges was broken and allowed traffic from any IP. The problem has been patched in v1.6.0. As a workaround, those who want to test challenges privately can mark them as `public: false` and use `kctf chal debug port-forward` to connect.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-06-13T20:17:12.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/sighting/b32639c9-1f36-435b-a44d-1e3b389231ee/export</guid>
      <pubDate>Mon, 13 Jun 2022 20:17:12 +0000</pubDate>
    </item>
  </channel>
</rss>
