<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic GlobalProtect, Release Notes, Build Numbers, CVE ?!?! in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-release-notes-build-numbers-cve/m-p/1254395#M7382</link>
    <description>&lt;P&gt;Can someone explain to me why the GlobalProtect App release notes don't list the CVE's addressed?&amp;nbsp; These are changes made in the app that need to be in the release notes and it seems unnecessary to have to check two different sources for information.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The only place CVE's are listed for GlobalProtect seems to be here:&amp;nbsp;&lt;A href="https://security.paloaltonetworks.com/" target="_blank"&gt;https://security.paloaltonetworks.com/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Also, what is it with Palo Alto and seemingly Cisco too with 6.3.3-h10 being listed but then on other locations being listed with a build&amp;nbsp;&amp;nbsp;# such as c1011. Either call it one or the other but not both.&amp;nbsp; The security site lists h11 now for a CVE that was showing 6.3.3-h10 the other day but since it isn't in any release notes it appears no one is being notified of this. If I hadn't checked today I'd have though deploying 6.3.3-h10 was going to fix&amp;nbsp;&lt;A href="https://security.paloaltonetworks.com/CVE-2026-0251" target="_blank"&gt;https://security.paloaltonetworks.com/CVE-2026-0251&lt;/A&gt;&amp;nbsp;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Sorry this is a bit of a rant so this is mainly intended for Palo Alto but good grief lets get some consistency. If you want to use both numbers use them both everywhere.&lt;/P&gt;</description>
    <pubDate>Wed, 20 May 2026 12:17:15 GMT</pubDate>
    <dc:creator>TonyDeHart</dc:creator>
    <dc:date>2026-05-20T12:17:15Z</dc:date>
    <item>
      <title>GlobalProtect, Release Notes, Build Numbers, CVE ?!?!</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-release-notes-build-numbers-cve/m-p/1254395#M7382</link>
      <description>&lt;P&gt;Can someone explain to me why the GlobalProtect App release notes don't list the CVE's addressed?&amp;nbsp; These are changes made in the app that need to be in the release notes and it seems unnecessary to have to check two different sources for information.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The only place CVE's are listed for GlobalProtect seems to be here:&amp;nbsp;&lt;A href="https://security.paloaltonetworks.com/" target="_blank"&gt;https://security.paloaltonetworks.com/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Also, what is it with Palo Alto and seemingly Cisco too with 6.3.3-h10 being listed but then on other locations being listed with a build&amp;nbsp;&amp;nbsp;# such as c1011. Either call it one or the other but not both.&amp;nbsp; The security site lists h11 now for a CVE that was showing 6.3.3-h10 the other day but since it isn't in any release notes it appears no one is being notified of this. If I hadn't checked today I'd have though deploying 6.3.3-h10 was going to fix&amp;nbsp;&lt;A href="https://security.paloaltonetworks.com/CVE-2026-0251" target="_blank"&gt;https://security.paloaltonetworks.com/CVE-2026-0251&lt;/A&gt;&amp;nbsp;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Sorry this is a bit of a rant so this is mainly intended for Palo Alto but good grief lets get some consistency. If you want to use both numbers use them both everywhere.&lt;/P&gt;</description>
      <pubDate>Wed, 20 May 2026 12:17:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-release-notes-build-numbers-cve/m-p/1254395#M7382</guid>
      <dc:creator>TonyDeHart</dc:creator>
      <dc:date>2026-05-20T12:17:15Z</dc:date>
    </item>
  </channel>
</rss>

