<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Niranj Maheswar</title>
    <description>The latest articles on DEV Community by Niranj Maheswar (@destawell).</description>
    <link>https://dev.to/destawell</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3945694%2F06bd51c3-ed58-4da8-9d67-a50bc5eb49f3.png</url>
      <title>DEV Community: Niranj Maheswar</title>
      <link>https://dev.to/destawell</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/destawell"/>
    <language>en</language>
    <item>
      <title>Case Study : Tracking Gemini 2.5 Pro's Safety Alignment &amp; Refusal Behaviour on CVE-2023-32233</title>
      <dc:creator>Niranj Maheswar</dc:creator>
      <pubDate>Fri, 22 May 2026 08:56:42 +0000</pubDate>
      <link>https://dev.to/destawell/case-study-tracking-gemini-25-pros-safety-alignment-refusal-behaviour-on-cve-2023-32233-5702</link>
      <guid>https://dev.to/destawell/case-study-tracking-gemini-25-pros-safety-alignment-refusal-behaviour-on-cve-2023-32233-5702</guid>
      <description>&lt;p&gt;Hey everyone,&lt;/p&gt;

&lt;p&gt;I wanted to share a quick technical case study I put together tracking how frontier LLMs—specifically &lt;strong&gt;Gemini 2.5 Pro&lt;/strong&gt;—handle specific prompt boundaries regarding &lt;strong&gt;CVE-2023-32233&lt;/strong&gt; (the known Use-After-Free flaw in the Linux kernel netfilter/nf_tables component).&lt;/p&gt;

&lt;p&gt;The research maps out a clear timeline tracking:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;How the model initially processed requests for technical exploitation primitives back in April.&lt;/li&gt;
&lt;li&gt;The rolling updates and full refusal behaviors implemented following recent safety alignment patches in mid-May.&lt;/li&gt;
&lt;/ul&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; No functional exploit code is hosted or shared. This repository is purely a documentation piece focused on the evolution of LLM guardrails, defensive safety metrics, and responsible disclosure tracking.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The full repository, logs, and boundary analysis are completely open-source:&lt;/p&gt;

&lt;p&gt;👉 &lt;strong&gt;GitHub Repository:&lt;/strong&gt; &lt;a href="https://github.com/Destawell/gemini-2.5-pro-nf-tables-red-teaming" rel="noopener noreferrer"&gt;https://github.com/Destawell/gemini-2.5-pro-nf-tables-red-teaming&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I’d love to hear insights from anyone else tracking LLM boundary shifts, jailbreak prevention mechanics, or automated patch cycles in commercial models!&lt;/p&gt;

</description>
      <category>security</category>
      <category>ai</category>
      <category>opensource</category>
      <category>linux</category>
    </item>
  </channel>
</rss>
