<?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>Fri, 01 May 2026 19:15:56 +0000</lastBuildDate>
    <item>
      <title>119224dd-0c9a-4ea3-8419-3d4613b28814</title>
      <link>https://db.gcve.eu/sighting/119224dd-0c9a-4ea3-8419-3d4613b28814/export</link>
      <description>{"uuid": "119224dd-0c9a-4ea3-8419-3d4613b28814", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2021-26073", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/4141", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2021-26073\n\ud83d\udd25 CVSS Score: 7.6 (CVSS_V3)\n\ud83d\udd39 Description: Broken Authentication in Atlassian Connect Express (ACE) from version 3.0.2 before version 6.6.0: Atlassian Connect Express is a Node.js package for building Atlassian Connect apps. Authentication between Atlassian products and the Atlassian Connect Express app occurs with a server-to-server JWT or a context JWT. Atlassian Connect Express versions between 3.0.2 - 6.5.0 erroneously accept context JWTs in lifecycle endpoints (such as installation) where only server-to-server JWTs should be accepted, permitting an attacker to send authenticated re-installation events to an app.\n\ud83d\udccf Published: 2022-05-24T22:28:12Z\n\ud83d\udccf Modified: 2025-02-12T21:53:02Z\n\ud83d\udd17 References:\n1. https://nvd.nist.gov/vuln/detail/CVE-2021-26073\n2. https://community.developer.atlassian.com/t/action-required-atlassian-connect-vulnerability-a%5B%E2%80%A6%5Dypass-of-app-qsh-verification-via-context-jwts/47072\n3. https://confluence.atlassian.com/pages/viewpage.action?pageId=1051986099\n4. https://security.netapp.com/advisory/ntap-20210604-0004\n5. http://bitbucket.org/atlassian/atlassian-connect-express", "creation_timestamp": "2025-02-12T22:10:44.000000Z"}</description>
      <content:encoded>{"uuid": "119224dd-0c9a-4ea3-8419-3d4613b28814", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2021-26073", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/4141", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2021-26073\n\ud83d\udd25 CVSS Score: 7.6 (CVSS_V3)\n\ud83d\udd39 Description: Broken Authentication in Atlassian Connect Express (ACE) from version 3.0.2 before version 6.6.0: Atlassian Connect Express is a Node.js package for building Atlassian Connect apps. Authentication between Atlassian products and the Atlassian Connect Express app occurs with a server-to-server JWT or a context JWT. Atlassian Connect Express versions between 3.0.2 - 6.5.0 erroneously accept context JWTs in lifecycle endpoints (such as installation) where only server-to-server JWTs should be accepted, permitting an attacker to send authenticated re-installation events to an app.\n\ud83d\udccf Published: 2022-05-24T22:28:12Z\n\ud83d\udccf Modified: 2025-02-12T21:53:02Z\n\ud83d\udd17 References:\n1. https://nvd.nist.gov/vuln/detail/CVE-2021-26073\n2. https://community.developer.atlassian.com/t/action-required-atlassian-connect-vulnerability-a%5B%E2%80%A6%5Dypass-of-app-qsh-verification-via-context-jwts/47072\n3. https://confluence.atlassian.com/pages/viewpage.action?pageId=1051986099\n4. https://security.netapp.com/advisory/ntap-20210604-0004\n5. http://bitbucket.org/atlassian/atlassian-connect-express", "creation_timestamp": "2025-02-12T22:10:44.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/sighting/119224dd-0c9a-4ea3-8419-3d4613b28814/export</guid>
      <pubDate>Wed, 12 Feb 2025 22:10:44 +0000</pubDate>
    </item>
    <item>
      <title>b97fa1a6-c7bd-4a63-9634-95a1e47eec79</title>
      <link>https://db.gcve.eu/sighting/b97fa1a6-c7bd-4a63-9634-95a1e47eec79/export</link>
      <description>{"uuid": "b97fa1a6-c7bd-4a63-9634-95a1e47eec79", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2021-26073", "type": "seen", "source": "Telegram/IOGuex9a_4cbtEZkxZFvO-SRovX9ZmHKc06-xUnov3f0DXiu", "content": "", "creation_timestamp": "2025-02-14T10:06:00.000000Z"}</description>
      <content:encoded>{"uuid": "b97fa1a6-c7bd-4a63-9634-95a1e47eec79", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2021-26073", "type": "seen", "source": "Telegram/IOGuex9a_4cbtEZkxZFvO-SRovX9ZmHKc06-xUnov3f0DXiu", "content": "", "creation_timestamp": "2025-02-14T10:06:00.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/sighting/b97fa1a6-c7bd-4a63-9634-95a1e47eec79/export</guid>
      <pubDate>Fri, 14 Feb 2025 10:06:00 +0000</pubDate>
    </item>
  </channel>
</rss>
