<?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 23:09:53 +0000</lastBuildDate>
    <item>
      <title>13d07c34-0adb-496c-accf-4b9f766af390</title>
      <link>https://vulnerability.circl.lu/sighting/13d07c34-0adb-496c-accf-4b9f766af390/export</link>
      <description>{"uuid": "13d07c34-0adb-496c-accf-4b9f766af390", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-39287", "type": "seen", "source": "https://t.me/cibsecurity/51045", "content": "\u203c CVE-2022-39287 \u203c\n\ntiny-csrf is a Node.js cross site request forgery (CSRF) protection middleware. In versions prior to 1.1.0 cookies were not encrypted and thus CSRF tokens were transmitted in the clear. This issue has been addressed in commit `8eead6d` and the patch with be included in version 1.1.0. Users are advised to upgrade. There are no known workarounds for this issue.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-10-08T00:17:57.000000Z"}</description>
      <content:encoded>{"uuid": "13d07c34-0adb-496c-accf-4b9f766af390", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2022-39287", "type": "seen", "source": "https://t.me/cibsecurity/51045", "content": "\u203c CVE-2022-39287 \u203c\n\ntiny-csrf is a Node.js cross site request forgery (CSRF) protection middleware. In versions prior to 1.1.0 cookies were not encrypted and thus CSRF tokens were transmitted in the clear. This issue has been addressed in commit `8eead6d` and the patch with be included in version 1.1.0. Users are advised to upgrade. There are no known workarounds for this issue.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2022-10-08T00:17:57.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/13d07c34-0adb-496c-accf-4b9f766af390/export</guid>
      <pubDate>Sat, 08 Oct 2022 00:17:57 +0000</pubDate>
    </item>
  </channel>
</rss>
