<?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, 02 Oct 2026 15:49:25 +0000</lastBuildDate>
    <item>
      <title>07a904ee-0589-4040-a65c-a9b33fe0ce69</title>
      <link>https://vulnerability.circl.lu/sighting/07a904ee-0589-4040-a65c-a9b33fe0ce69/export</link>
      <description>{"uuid": "07a904ee-0589-4040-a65c-a9b33fe0ce69", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2026-103655", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/117365745916061544", "content": "This is an interesting vuln and one that can be a great example of why a sev:CRIT may not be high priority.\nsev:CRIT 9.3 - CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N\n\nMISP contains a vulnerability in its two-factor authentication (TOTP) verification process that permits a valid one-time code to be accepted more than once within its time-based validity window. The issue exists in the user login flow where a TOTP code is verified as a second authentication factor. Because the system did not record whether a given TOTP period had already been consumed, the same code remained valid for its entire time window (typically 30 seconds). An attacker who captures a legitimate code during a user's login could replay it to authenticate a second session as that user. Preconditions: - The target user has TOTP-based two-factor authentication enabled. - The attacker is in a position to observe or intercept the TOTP code during a legitimate login (e.g., network-level interception, shoulder surfing, or a compromised client). - The replay must occur within the TOTP validity period. Security impact: - Unauthorized account access by replaying a captured one-time code. - Potential compromise of threat-intelligence data and administrative functions accessible to the targeted user. Affected versions: &amp;lt;v2.5.48.\nhttps://nvd.nist.gov/vuln/detail/cve-2026-103655", "creation_timestamp": "2026-10-01T12:52:42.060705Z"}</description>
      <content:encoded>{"uuid": "07a904ee-0589-4040-a65c-a9b33fe0ce69", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2026-103655", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/117365745916061544", "content": "This is an interesting vuln and one that can be a great example of why a sev:CRIT may not be high priority.\nsev:CRIT 9.3 - CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N\n\nMISP contains a vulnerability in its two-factor authentication (TOTP) verification process that permits a valid one-time code to be accepted more than once within its time-based validity window. The issue exists in the user login flow where a TOTP code is verified as a second authentication factor. Because the system did not record whether a given TOTP period had already been consumed, the same code remained valid for its entire time window (typically 30 seconds). An attacker who captures a legitimate code during a user's login could replay it to authenticate a second session as that user. Preconditions: - The target user has TOTP-based two-factor authentication enabled. - The attacker is in a position to observe or intercept the TOTP code during a legitimate login (e.g., network-level interception, shoulder surfing, or a compromised client). - The replay must occur within the TOTP validity period. Security impact: - Unauthorized account access by replaying a captured one-time code. - Potential compromise of threat-intelligence data and administrative functions accessible to the targeted user. Affected versions: &amp;lt;v2.5.48.\nhttps://nvd.nist.gov/vuln/detail/cve-2026-103655", "creation_timestamp": "2026-10-01T12:52:42.060705Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/07a904ee-0589-4040-a65c-a9b33fe0ce69/export</guid>
      <pubDate>Thu, 01 Oct 2026 12:52:42 +0000</pubDate>
    </item>
    <item>
      <title>6269c1bb-1bb8-4a6b-8433-7ebdf37ad149</title>
      <link>https://vulnerability.circl.lu/sighting/6269c1bb-1bb8-4a6b-8433-7ebdf37ad149/export</link>
      <description>{"uuid": "6269c1bb-1bb8-4a6b-8433-7ebdf37ad149", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-103655", "type": "seen", "source": "https://bsky.app/profile/stemshop.bsky.social/post/3mwsmfezd2e2o", "content": "\ud83d\udea8 CVE-2026-103655 \u2014 CVSS 9.3 CRITICAL\n\nMISP contains a vulnerability in its two-factor authentication (TOTP) verification process that permits a v...\n\n\ud83d\udd0e https://stemshop.top/cve/CVE-2026-103655\n\n#CVE #CyberSecurity #InfoSec", "creation_timestamp": "2026-10-01T10:07:52.218619Z"}</description>
      <content:encoded>{"uuid": "6269c1bb-1bb8-4a6b-8433-7ebdf37ad149", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-103655", "type": "seen", "source": "https://bsky.app/profile/stemshop.bsky.social/post/3mwsmfezd2e2o", "content": "\ud83d\udea8 CVE-2026-103655 \u2014 CVSS 9.3 CRITICAL\n\nMISP contains a vulnerability in its two-factor authentication (TOTP) verification process that permits a v...\n\n\ud83d\udd0e https://stemshop.top/cve/CVE-2026-103655\n\n#CVE #CyberSecurity #InfoSec", "creation_timestamp": "2026-10-01T10:07:52.218619Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/6269c1bb-1bb8-4a6b-8433-7ebdf37ad149/export</guid>
      <pubDate>Thu, 01 Oct 2026 10:07:52 +0000</pubDate>
    </item>
  </channel>
</rss>
