<?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>Sonicwall on Caleb Garber</title>
    <link>https://calebgarber.com/tags/sonicwall/</link>
    <description>Recent content in Sonicwall on Caleb Garber</description>
    <generator>Hugo -- 0.165.0</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 09 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://calebgarber.com/tags/sonicwall/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CVE Watch: 7 November 2026, an exploited SonicWall SSLVPN bypass on a federal deadline</title>
      <link>https://calebgarber.com/posts/cve-watch-2026-11-07/</link>
      <pubDate>Mon, 09 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://calebgarber.com/posts/cve-watch-2026-11-07/</guid>
      <description>The 7 November batch carries seven SonicWall SonicOS records from one advisory. CVE-2026-19868 is on the KEV catalog with a 20 November deadline, and it only applies where SAML is enabled for SSLVPN logins. The same firmware closes the other six.</description>
    </item>
    <item>
      <title>CVE-2026-19868 is a 7.5 from CISA-ADP and a 7.1 from SonicWall, and the SAML policy covers one login path</title>
      <link>https://calebgarber.com/posts/cve-2026-19868-is-a-7-5-in-sonicwall-sonicos/</link>
      <pubDate>Sun, 08 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://calebgarber.com/posts/cve-2026-19868-is-a-7-5-in-sonicwall-sonicos/</guid>
      <description>SonicWall&amp;#39;s CVE-2026-19868 lets a valid credential for an alternate authentication method bypass SAML and the MFA it enforces on the SSLVPN service. What the advisory covers, why SonicWall&amp;#39;s 7.1 and the CISA-ADP 7.5 that NVD displays differ by one field, and the authentication inventory I run on the remote access paths I do assess.</description>
    </item>
  </channel>
</rss>
