<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>CVE-2025-3263 on Arjun&#39;s Blog</title>
    <link>/tags/cve-2025-3263/</link>
    <description>Recent content in CVE-2025-3263 on Arjun&#39;s Blog</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 27 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/cve-2025-3263/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>6 CVEs and $750: Automating ReDoS Vulnerability Discovery with AI</title>
      <link>/posts/6-redos-vulnerability-automation-with-ai/</link>
      <pubDate>Mon, 27 Apr 2026 00:00:00 +0000</pubDate>
      <guid>/posts/6-redos-vulnerability-automation-with-ai/</guid>
      <description>&lt;p&gt;The idea started while browsing &lt;a href=&#34;https://huntr.com/bounties/hacktivity&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;Huntr&amp;rsquo;s hacktivity&lt;/a&gt;&#xA;&#xA;feed. I saw a ReDoS vulnerability reported in HuggingFace Transformers and wondered how many more might be hiding in there. Manually reviewing regex patterns sounded tedious and I only have the attention span of a Skink, so naturally I spent time building a tool to avoid doing it myself. That laziness paid off — 6 CVEs and $750, to be exact.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-even-is-redos&#34;&gt;What Even is ReDoS?&lt;/h2&gt;&#xA;&lt;p&gt;Before we dive in, let me explain what ReDoS (Regular Expression Denial of Service) is for the uninitiated.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
