<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Python-Security on Napat&#39;s Inverse Blog</title>
    <link>/tags/python-security/</link>
    <description>Recent content in Python-Security on Napat&#39;s Inverse Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 19 Jun 2026 17:30:00 +0700</lastBuildDate>
    <atom:link href="/tags/python-security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Six Phases, Twelve Agents, One Flask Library: A Day With Cloudflare&#39;s Vulnerability Harness</title>
      <link>/ai-analysis/six-phases-twelve-agents-one-flask-library/</link>
      <pubDate>Fri, 19 Jun 2026 17:30:00 +0700</pubDate>
      <guid>/ai-analysis/six-phases-twelve-agents-one-flask-library/</guid>
      <description>&lt;p&gt;I have a bad habit. When I read a good blog post, I read it once, nod, and never actually try the thing it describes.&lt;/p&gt;
&lt;p&gt;This time I was determined to break that pattern. The post was &lt;a href=&#34;https://blog.cloudflare.com/build-your-own-vulnerability-harness/&#34;&gt;Cloudflare&amp;rsquo;s &amp;ldquo;Build Your Own Vulnerability Harness&amp;rdquo;&lt;/a&gt;. It described a 6-phase multi-agent security audit pipeline. I had been wanting to test something like this for months. So I read the post, closed the tab, and opened a terminal.&lt;/p&gt;
&lt;p&gt;This is what happened next. The good parts, the embarrassing parts, and the part where I found a real authentication bypass in a 6,000-line Python library that downloads 50 million times a month.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
