<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>SYRN Blog</title>
    <link>https://syrn.fr/en/blog</link>
    <description>Latest articles from the SYRN blog on vulnerability management, CVE prioritization, and threat intelligence.</description>
    <language>en</language>
    <atom:link href="https://syrn.fr/blog-feed-en.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>Don't Take Wednesday Off When You Manage Vulnerabilities</title>
      <link>https://syrn.fr/en/blog/dont-take-wednesday-off-cve-patch-tuesday</link>
      <guid isPermaLink="true">https://syrn.fr/en/blog/dont-take-wednesday-off-cve-patch-tuesday</guid>
      <pubDate>Tue, 02 Jun 2026 08:00:00 GMT</pubDate>
      <description>We analyzed 355,000 CVEs and CISA's entire KEV catalog. Patch Tuesday is a decoy: the real disclosure peak is Wednesday. A (tongue-in-cheek) guide to when not to take time off in vulnerability management.</description>
    </item>
    <item>
      <title>50,000 CVEs in 2025, 70,000 in 2026: Why Prioritization Is the Real Challenge</title>
      <link>https://syrn.fr/en/blog/50000-cves-2025-prioritization-real-challenge</link>
      <guid isPermaLink="true">https://syrn.fr/en/blog/50000-cves-2025-prioritization-real-challenge</guid>
      <pubDate>Sun, 24 May 2026 08:00:00 GMT</pubDate>
      <description>Nearly 50,000 CVEs in 2025, 70,000 expected in 2026, yet less than 1% are actually exploited. Why CVSS and EPSS are no longer enough to decide what to patch.</description>
    </item>
    <item>
      <title>Welcome to the SYRN Blog</title>
      <link>https://syrn.fr/en/blog/welcome-to-syrn-blog</link>
      <guid isPermaLink="true">https://syrn.fr/en/blog/welcome-to-syrn-blog</guid>
      <pubDate>Sat, 07 Mar 2026 08:00:00 GMT</pubDate>
      <description>Introducing the SYRN blog: your source for cybersecurity insights, threat intelligence updates, and vulnerability management best practices.</description>
    </item>
  </channel>
</rss>
