Add latest releases
This commit is contained in:
@@ -0,0 +1,61 @@
|
|||||||
|
<table class="table colsep rowsep table-striped">
|
||||||
|
<!--cq:include script="../../common/tablestack.jsp" /-->
|
||||||
|
|
||||||
|
<colgroup>
|
||||||
|
<col style="width: 25%" />
|
||||||
|
<col style="width: 75%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead class="thead">
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<th class="entry">
|
||||||
|
<div class="p"><b class="ph b">Issue ID</b></div>
|
||||||
|
</th>
|
||||||
|
<th class="entry">
|
||||||
|
<div class="p"><b class="ph b">Description</b></div>
|
||||||
|
</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
|
||||||
|
<tbody class="tbody">
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-301222</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where DNS Security logs incorrectly displayed a
|
||||||
|
sinkhole action for benign DNS categories due to the firewall saving
|
||||||
|
the drop or sinkhole action in session flags without discarding the
|
||||||
|
session.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-291653</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where the GlobalProtect host ID field was
|
||||||
|
intermittently blank in traffic logs on Prisma Access, even when the
|
||||||
|
user was connected and had the correct host ID information. This
|
||||||
|
occurred when the IP address to host ID entry expired and the entry
|
||||||
|
was re-inserted without the dataplane flag being set.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-195264</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where the login lifetime countdown timer reset when
|
||||||
|
using an authentication override cookie to log in to the gateway.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
@@ -0,0 +1,54 @@
|
|||||||
|
<table class="table colsep rowsep table-striped">
|
||||||
|
<!--cq:include script="../../common/tablestack.jsp" /-->
|
||||||
|
|
||||||
|
<colgroup>
|
||||||
|
<col style="width: 25%" />
|
||||||
|
<col style="width: 75%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead class="thead">
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<th class="entry">
|
||||||
|
<div class="p"><b class="ph b">Issue ID</b></div>
|
||||||
|
</th>
|
||||||
|
<th class="entry">
|
||||||
|
<div class="p"><b class="ph b">Description</b></div>
|
||||||
|
</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
|
||||||
|
<tbody class="tbody">
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-312703</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where failures between
|
||||||
|
<a
|
||||||
|
class="term"
|
||||||
|
href="#"
|
||||||
|
title=""
|
||||||
|
data-scope=""
|
||||||
|
data-format="dita"
|
||||||
|
data-type=""
|
||||||
|
target="_self"
|
||||||
|
>useridd</a
|
||||||
|
>
|
||||||
|
and
|
||||||
|
<a
|
||||||
|
class="term"
|
||||||
|
href="#"
|
||||||
|
title=""
|
||||||
|
data-scope=""
|
||||||
|
data-format="dita"
|
||||||
|
data-type=""
|
||||||
|
target="_self"
|
||||||
|
>logrcvr</a
|
||||||
|
>
|
||||||
|
processes could lead to intermittent loss of User-ID and HIP Match
|
||||||
|
logs during log spikes.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
@@ -0,0 +1,139 @@
|
|||||||
|
<table class="table colsep rowsep table-striped">
|
||||||
|
<!--cq:include script="../../common/tablestack.jsp" /-->
|
||||||
|
|
||||||
|
<colgroup>
|
||||||
|
<col style="width: 25.062656641604008%" />
|
||||||
|
<col style="width: 74.93734335839599%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead class="thead">
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<th class="entry">
|
||||||
|
<div class="p"><b class="ph b">Issue ID</b></div>
|
||||||
|
</th>
|
||||||
|
<th class="entry">
|
||||||
|
<div class="p"><b class="ph b">Description</b></div>
|
||||||
|
</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
|
||||||
|
<tbody class="tbody">
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">—</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">Fixes were made to address the following CVEs:</div>
|
||||||
|
<ul id="pan-os-10-2-10-h31-addressed-issues_ul-snk_4r1_gjc" class="ul">
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0265"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0265</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0264"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0264</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0262"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0262</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0261"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0261</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0258"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0258</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0257"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0257</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0256"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0256</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0259"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0259</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0300"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0300</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
</ul>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
@@ -0,0 +1,35 @@
|
|||||||
|
<table class="table colsep rowsep table-striped">
|
||||||
|
<!--cq:include script="../../common/tablestack.jsp" /-->
|
||||||
|
|
||||||
|
<colgroup>
|
||||||
|
<col style="width: 38%" />
|
||||||
|
<col style="width: 62%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead class="thead">
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<th class="entry">
|
||||||
|
<div class="p"><b class="ph b">Issue ID</b></div>
|
||||||
|
</th>
|
||||||
|
<th class="entry">
|
||||||
|
<div class="p"><b class="ph b">Description</b></div>
|
||||||
|
</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
|
||||||
|
<tbody class="tbody">
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-306502</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where TLS connection failure occurred when traffic was
|
||||||
|
over TLS1.2 or below, header insertion was enabled on the firewall,
|
||||||
|
<span class="ph uicontrol">send TLS handshake to CTD</span> was
|
||||||
|
enabled, and traffic hit a decryption policy rule configured with the
|
||||||
|
<span class="ph uicontrol">no-decrypt</span> action.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
@@ -0,0 +1,405 @@
|
|||||||
|
<table class="table colsep rowsep table-striped">
|
||||||
|
<!--cq:include script="../../common/tablestack.jsp" /-->
|
||||||
|
|
||||||
|
<colgroup>
|
||||||
|
<col style="width: 25%" />
|
||||||
|
<col style="width: 75%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead class="thead">
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<th class="entry">
|
||||||
|
<div class="p"><b class="ph b">Issue ID</b></div>
|
||||||
|
</th>
|
||||||
|
<th class="entry">
|
||||||
|
<div class="p"><b class="ph b">Description</b></div>
|
||||||
|
</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
|
||||||
|
<tbody class="tbody">
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-316911</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
(<tt class="ph tt"
|
||||||
|
>VM-Series firewalls on Amazon Web Services (AWS) environments
|
||||||
|
only</tt
|
||||||
|
>) Fixed an issue where a newly bootstrapped firewall required a
|
||||||
|
management server restart, relicensing, or license push from Panorama
|
||||||
|
to invoke the device certificate.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-312706</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where the firewalls restarted due to a function lacking
|
||||||
|
a NULL-pointer sanity check.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-308507</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
(<tt class="ph tt">Panorama managed firewalls only</tt>) Fixed an
|
||||||
|
issue where the firewall intermittently failed to maintain active log
|
||||||
|
forwarding streams to Strata Logging Service (SLS) even when duplicate
|
||||||
|
logging and enhanced application logging were enabled.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-307795</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where Panorama incorrectly generated system logs
|
||||||
|
indicating a lost connection to its peer after an upgrade even when
|
||||||
|
High Availability was not configured.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-307597</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where BGP peering sessions between a hub firewall and a
|
||||||
|
satellite firewall over GlobalProtect LSVPN failed to connect.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-305415</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where commits caused high dataplane CPU utilization and
|
||||||
|
briefly increased Packet Descriptors, which disrupted traffic.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-304756</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue on Panorama where, after you disabled the shared
|
||||||
|
optimization feature, a full configuration push to multi-vsys devices
|
||||||
|
caused a validation error.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-303051</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue on Panorama where a memory leak occurred related to the
|
||||||
|
<a
|
||||||
|
class="term"
|
||||||
|
href="#"
|
||||||
|
title=""
|
||||||
|
data-scope=""
|
||||||
|
data-format="dita"
|
||||||
|
data-type=""
|
||||||
|
target="_self"
|
||||||
|
>reportd</a
|
||||||
|
>
|
||||||
|
process due to retaining memory that was temporarily used for report
|
||||||
|
generation instead of releasing the memory for reuse, which resulted
|
||||||
|
in continuous accumulation and memory exhaustion.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-301409</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where Panorama failed to perform a selective push to a
|
||||||
|
managed device when device tags were added or modified on the policy
|
||||||
|
rules. The selective push would fail with the error message
|
||||||
|
<span class="ph systemoutput"
|
||||||
|
>Failed to generate selective push configuration. Schema validation
|
||||||
|
failed. Please try a full push</span
|
||||||
|
>.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-300671</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where traffic reports that were generated with
|
||||||
|
destination/source and destination/source hostnames were not displayed
|
||||||
|
in IPv4 format.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-297610</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where the firewall became unresponsive after an upgrade
|
||||||
|
due to the
|
||||||
|
<a
|
||||||
|
class="term"
|
||||||
|
href="#"
|
||||||
|
title=""
|
||||||
|
data-scope=""
|
||||||
|
data-format="dita"
|
||||||
|
data-type=""
|
||||||
|
target="_self"
|
||||||
|
>fsck</a
|
||||||
|
>
|
||||||
|
command scanning drive partitions in parallel with the root partition,
|
||||||
|
which caused the process to take an extended amount of time.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-295470</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue on the firewall where the
|
||||||
|
<a
|
||||||
|
class="term"
|
||||||
|
href="#"
|
||||||
|
title=""
|
||||||
|
data-scope=""
|
||||||
|
data-format="dita"
|
||||||
|
data-type=""
|
||||||
|
target="_self"
|
||||||
|
>useridd</a
|
||||||
|
>
|
||||||
|
process continuously increased its memory consumption, which resulted
|
||||||
|
in an OOM condition that caused the firewall to restart.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-291067</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where the
|
||||||
|
<a
|
||||||
|
class="term"
|
||||||
|
href="#"
|
||||||
|
title=""
|
||||||
|
data-scope=""
|
||||||
|
data-format="dita"
|
||||||
|
data-type=""
|
||||||
|
target="_self"
|
||||||
|
>devsrvr</a
|
||||||
|
>
|
||||||
|
process periodically exceeded its virtual memory limit and restarted,
|
||||||
|
which led to intermittent outages.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-291009</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where, after a web server returned a 401 or 403 error,
|
||||||
|
the firewall was unable to decrypt HTTP/2 traffic, and the firewall
|
||||||
|
rejected all subsequent streams from the client.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b"> PAN-289249</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where a memory leak occurred on the
|
||||||
|
<a
|
||||||
|
class="term"
|
||||||
|
href="#"
|
||||||
|
title=""
|
||||||
|
data-scope=""
|
||||||
|
data-format="dita"
|
||||||
|
data-type=""
|
||||||
|
target="_self"
|
||||||
|
>reportd</a
|
||||||
|
>
|
||||||
|
process when a WildFire update was initiated while device telemetry
|
||||||
|
data collection was in progress. This resulted in an OOM condition.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-284067</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed a cumulative memory leak in the
|
||||||
|
<a
|
||||||
|
class="term"
|
||||||
|
href="#"
|
||||||
|
title=""
|
||||||
|
data-scope=""
|
||||||
|
data-format="dita"
|
||||||
|
data-type=""
|
||||||
|
target="_self"
|
||||||
|
>devsrvr</a
|
||||||
|
>
|
||||||
|
process that occurred whenever the CLI command
|
||||||
|
<span class="ph systemoutput"
|
||||||
|
>show running application statistics</span
|
||||||
|
>
|
||||||
|
was issued. This memory leak would gradually consume system memory and
|
||||||
|
produce an OOM condition, causing the firewall to reboot.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-280196</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue in Prisma Access environments where the firewall
|
||||||
|
matched a HIP object but not on the HIP profile that contained the
|
||||||
|
object.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-279364</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
(<tt class="ph tt">VM-Series firewalls with multiple NICs only</tt>)
|
||||||
|
Fixed an issue were the queue count in the task dump displayed an
|
||||||
|
incorrect number of queues for SR-IOV interfaces due to the queue
|
||||||
|
mapping logic incorrectly using a non-multi-NIC function.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-274742</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
(<tt class="ph tt">VM-Series firewalls only</tt>) Fixed an issue where
|
||||||
|
the <span class="ph systemoutput">task-queue dump</span> CLI command
|
||||||
|
returned incorrect information in multi-nic mode.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-261825</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where traffic was dropped when Data Loss Prevention or
|
||||||
|
Advanced URL Filtering were enabled. This occurred when the payload
|
||||||
|
size was greater than 3.5 KB.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-252809</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where a single PIM neighbor was sending 0.0.0.0 as its
|
||||||
|
address, which occurred because an improvement in PIM neighbor address
|
||||||
|
selection did not correctly account for configurations with a single
|
||||||
|
IP address.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-242952</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where high SSL traffic depleted flex memory, which
|
||||||
|
prevented the firewall from revalidating SSLVPN client CAs during
|
||||||
|
configuration pushes.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-230748</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where the firewall displayed the current time as the
|
||||||
|
expiration date for an imported certificate in the CLI output instead
|
||||||
|
of the correct expiry time due to an improper use of an OpenSSL
|
||||||
|
library function.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-202911</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where a satellite tunnel was not established after
|
||||||
|
turning on satellite firewalls.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
@@ -0,0 +1,139 @@
|
|||||||
|
<table class="table colsep rowsep table-striped">
|
||||||
|
<!--cq:include script="../../common/tablestack.jsp" /-->
|
||||||
|
|
||||||
|
<colgroup>
|
||||||
|
<col style="width: 25.062656641604008%" />
|
||||||
|
<col style="width: 74.93734335839599%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead class="thead">
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<th class="entry">
|
||||||
|
<div class="p"><b class="ph b">Issue ID</b></div>
|
||||||
|
</th>
|
||||||
|
<th class="entry">
|
||||||
|
<div class="p"><b class="ph b">Description</b></div>
|
||||||
|
</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
|
||||||
|
<tbody class="tbody">
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">—</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">Fixes were made to address the following CVEs:</div>
|
||||||
|
<ul id="pan-os-10-2-10-h31-addressed-issues_ul-snk_4r1_gjc" class="ul">
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0265"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0265</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0264"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0264</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0262"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0262</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0261"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0261</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0258"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0258</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0257"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0257</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0256"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0256</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0259"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0259</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0300"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0300</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
</ul>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
@@ -0,0 +1,406 @@
|
|||||||
|
<table class="table colsep rowsep table-striped">
|
||||||
|
<!--cq:include script="../../common/tablestack.jsp" /-->
|
||||||
|
|
||||||
|
<colgroup>
|
||||||
|
<col style="width: 25%" />
|
||||||
|
<col style="width: 75%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead class="thead">
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<th class="entry">
|
||||||
|
<div class="p"><b class="ph b">Issue ID</b></div>
|
||||||
|
</th>
|
||||||
|
<th class="entry">
|
||||||
|
<div class="p"><b class="ph b">Description</b></div>
|
||||||
|
</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
|
||||||
|
<tbody class="tbody">
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-303559</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where, after manuallly creating a device telemetry
|
||||||
|
bundle, the
|
||||||
|
<span class="ph systemoutput">hour_cli_output.txt</span> file within
|
||||||
|
the bundle had a file size of 0 bytes. This occurred when checking the
|
||||||
|
bundle content after enabling device telemetry and setting the device
|
||||||
|
telemetry upload endpoint.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-301018</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue on Panorama where API queries for correlated category
|
||||||
|
logs incorrectly returned a count of 0.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-300055</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where the firewall experienced high disk utilization in
|
||||||
|
the /opt/pancfg/mgmt/content-preview directory due to older content
|
||||||
|
data not being automatically removed when an error occurred during the
|
||||||
|
process.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-297775</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where, after upgrading to an affected PAN-OS release,
|
||||||
|
the Visible Virtual System field referenced the vsys name instead of
|
||||||
|
the vsys ID, which caused inter-vsys routing to fail. This occurred
|
||||||
|
when a vsys display name matched one of the vsys IDs. If you're using
|
||||||
|
a multivsys environment, you must upgrade your firewalls to a fixed
|
||||||
|
PAN-OS version. The best practice is to upgrade both the firewalls and
|
||||||
|
Panorama to a fixed PAN-OS version.
|
||||||
|
</div>
|
||||||
|
<ul class="ul">
|
||||||
|
<li class="li">
|
||||||
|
If you don't upgrade Panorama to a fixed version, you'll encounter
|
||||||
|
PAN-245064, where a commit on a multivsys firewall fails with the
|
||||||
|
message
|
||||||
|
<span class="ph systemoutput"
|
||||||
|
>vsys name should end with a number vsys is invalid</span
|
||||||
|
>
|
||||||
|
after you
|
||||||
|
<span class="ph uicontrol"
|
||||||
|
>Export or push device config bundle</span
|
||||||
|
>
|
||||||
|
from 11.1.1 Panorama.
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
After you upgrade Panorama to a fixed version, you'll encounter
|
||||||
|
PAN-214177, which causes an
|
||||||
|
<span class="ph uicontrol"
|
||||||
|
>Export or Push device config bundle</span
|
||||||
|
>
|
||||||
|
from Panorama to the firewall to fail. The workaround for PAN-214177
|
||||||
|
is to first push only the template configuration and then push the
|
||||||
|
device group configurations.
|
||||||
|
</li>
|
||||||
|
</ul>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-297708</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where a long-lived session with many Machine Learning
|
||||||
|
(ML) model triggers caused a memory leak of feature states associated
|
||||||
|
with the ML model runs. This resulted in Spyware_State failure
|
||||||
|
increases, allocation max outs, and impaired policy matching.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-297609</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where the the CLI command
|
||||||
|
<span class="ph systemoutput"
|
||||||
|
>debug user-id refresh user-id agent all</span
|
||||||
|
>
|
||||||
|
failed with the error message
|
||||||
|
<span class="ph systemoutput"
|
||||||
|
>Invalid agent name. Agent name should be 1 to 31 characters
|
||||||
|
long.</span
|
||||||
|
>
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-297261</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where the proxy-protocol debug level was set to
|
||||||
|
<span class="ph systemoutput">verbose</span> on Prisma Access
|
||||||
|
instances, even when it was not explicitly configured, which caused
|
||||||
|
excessive logging by the
|
||||||
|
<a
|
||||||
|
class="term"
|
||||||
|
href="#"
|
||||||
|
title=""
|
||||||
|
data-scope=""
|
||||||
|
data-format="dita"
|
||||||
|
data-type=""
|
||||||
|
target="_self"
|
||||||
|
>pan_task</a
|
||||||
|
>
|
||||||
|
process.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-295095</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where, when you used a syslog forwarding profile with
|
||||||
|
the CEF format, an additional string was appended to the end of the
|
||||||
|
log message when viewing the log entry from the Universal Forwarder
|
||||||
|
directory.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-295049</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where the
|
||||||
|
<a
|
||||||
|
class="term"
|
||||||
|
href="#"
|
||||||
|
title=""
|
||||||
|
data-scope=""
|
||||||
|
data-format="dita"
|
||||||
|
data-type=""
|
||||||
|
target="_self"
|
||||||
|
>logrcvr</a
|
||||||
|
>
|
||||||
|
process stopped responding due to memory allocation errors during
|
||||||
|
Redis communication.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-294893</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where firewalls with the
|
||||||
|
<span class="ph uicontrol"
|
||||||
|
>Send handshake messages to CTD for inspection</span
|
||||||
|
>
|
||||||
|
setting enabled caused incorrect security policy rules to be matched.
|
||||||
|
Specifically, traffic not identified as openai-base or openai-chatgpt
|
||||||
|
applications was incorrectly matched by the
|
||||||
|
ALLOW-OPEN-AI-FULL-ACCESS-URLS-ALERTS rule. Additionally, the expected
|
||||||
|
response page for blocked URLs was not displayed.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-292447</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where Panorama did not display data in the
|
||||||
|
<span class="ph uicontrol">Feature Adoption</span> tab in Strata Cloud
|
||||||
|
Manager due to the system creating and deleting a CLI user for each
|
||||||
|
interval instead of reusing a permanent CLI user for telemetry.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-291172</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where administrators were unable to gather path
|
||||||
|
monitoring failure information when troubleshooting high dataplane CPU
|
||||||
|
utilization.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-290665</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue with firewalls enabled with Security profiles where
|
||||||
|
certain traffic conditions caused high dataplane CPU utilization and
|
||||||
|
packet buffer exhaustion, which caused LACP flapping conditions.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-289067</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where, after upgrading Panorama in a High Availability
|
||||||
|
(HA) pair, the configuration logs stopped synchronizing from the
|
||||||
|
primary Panorama to the secondary Panorama. This issue occurred
|
||||||
|
because the log forwarding flag was permanently disabled due to the
|
||||||
|
connection state not being active when the
|
||||||
|
<span class="ph systemoutput">log-fwd-ctrl</span> message was
|
||||||
|
received.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-288097</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where on the firewall where the
|
||||||
|
<a
|
||||||
|
class="term"
|
||||||
|
href="#"
|
||||||
|
title=""
|
||||||
|
data-scope=""
|
||||||
|
data-format="dita"
|
||||||
|
data-type=""
|
||||||
|
target="_self"
|
||||||
|
>routed</a
|
||||||
|
>
|
||||||
|
process stopped responding after changing the MTU or any link state
|
||||||
|
parameters when OSPF and PIM were enabled on the same interface.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-287387</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue on Panorama where API jobs failed with the error
|
||||||
|
message
|
||||||
|
<span class="ph systemoutput"
|
||||||
|
>Server error: Timed out while getting config lock</span
|
||||||
|
>. This occurred due to slow set request performance when setting a
|
||||||
|
large number of address objects in a single set call.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-285208</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where the firewall did not automatically recover after
|
||||||
|
a machine check exception (MCE) occurred.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-283237</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where traffic logs incorrectly displayed the action as
|
||||||
|
<span class="ph uicontrol">allow</span> for traffic matching a
|
||||||
|
Security policy rule configured with the action set to
|
||||||
|
<span class="ph uicontrol">deny</span>. This issue occurred due to the
|
||||||
|
child session being used for policy rule lookup when a configuration
|
||||||
|
update triggered a rematch if the FTP-data application was not in the
|
||||||
|
rule.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-281588</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where packet buffer depletion occurred due to the a
|
||||||
|
high number of
|
||||||
|
<span class="ph systemoutput">tcp_pkt_queued</span> packets when Jumbo
|
||||||
|
was enabled.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-266843</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue on airgapped firewalls where cloud connection errors
|
||||||
|
flooded the system logs.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-262353</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where, when Panorama was upgraded to PAN-OS 10.2.10,
|
||||||
|
and log collectors were on PAN-OS 10.2.9-h1, logs from a log collector
|
||||||
|
group were not viewable on a Panorama.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-237349</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where URLs with over 965 characters were unable to be
|
||||||
|
logged in the URL filtering log.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-233542</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where the firewall did not display the source address
|
||||||
|
due to an uninitialized scalar variable.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
@@ -0,0 +1,341 @@
|
|||||||
|
<table class="table colsep rowsep table-striped">
|
||||||
|
<!--cq:include script="../../common/tablestack.jsp" /-->
|
||||||
|
|
||||||
|
<colgroup>
|
||||||
|
<col style="width: 25.062656641604008%" />
|
||||||
|
<col style="width: 74.93734335839599%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead class="thead">
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<th class="entry">
|
||||||
|
<div class="p"><b class="ph b">Issue ID</b></div>
|
||||||
|
</th>
|
||||||
|
<th class="entry">
|
||||||
|
<div class="p"><b class="ph b">Description</b></div>
|
||||||
|
</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
|
||||||
|
<tbody class="tbody">
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">—</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">Fixes were made to address the following CVEs:</div>
|
||||||
|
<ul id="pan_os_11_1_13_h5_addressed_issues_ul-snk_4r1_gjc" class="ul">
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0265"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0265</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0264"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0264</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0263"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0263</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0262"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0262</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0261"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0261</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0258"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0258</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0257"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0257</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0256"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0256</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0259"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0259</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0300"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0300</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
</ul>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-323243</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where a
|
||||||
|
<a
|
||||||
|
class="term"
|
||||||
|
href="#"
|
||||||
|
title=""
|
||||||
|
data-scope=""
|
||||||
|
data-format="dita"
|
||||||
|
data-type=""
|
||||||
|
target="_self"
|
||||||
|
>configd</a
|
||||||
|
>
|
||||||
|
crash occurred when the
|
||||||
|
<span class="ph uicontrol">Policies > Security</span> view was
|
||||||
|
updated or refreshed in the web interface.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-317215</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
(<tt class="ph tt"
|
||||||
|
>VM-Series firewalls on ESXi with Intel E810 NICs using PCI
|
||||||
|
passthrough</tt
|
||||||
|
>) Fixed an issue where the
|
||||||
|
<a
|
||||||
|
class="term"
|
||||||
|
href="#"
|
||||||
|
title=""
|
||||||
|
data-scope=""
|
||||||
|
data-format="dita"
|
||||||
|
data-type=""
|
||||||
|
target="_self"
|
||||||
|
>brdagent</a
|
||||||
|
>
|
||||||
|
process became unresponsive during data port initialization, which
|
||||||
|
resulted in system instability, interface outages, HA split-brain
|
||||||
|
conditions, and unexpected reboots during failover.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b"> PAN-317155</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where the link status of log port 1 and log port 2 were
|
||||||
|
unable to be monitored via SNMP due to the OIDs for the individual
|
||||||
|
ports not being available.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-314875</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
(<tt class="ph tt">PA-7500 firewalls only</tt>) Fixed an issue where
|
||||||
|
firewall logs were not visible in the Strata Logging Service even
|
||||||
|
though cloud logging was enabled and the firewall was successfully
|
||||||
|
forwarding logs.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-314126</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where session rematch did not properly apply updated
|
||||||
|
Security policy rules to existing traffic flows after committing
|
||||||
|
changes, which caused traffic to still be allowed when a new Security
|
||||||
|
policy was set to <span class="ph uicontrol">Deny</span>.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-311166</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where the firewall rebooted unexpectedly to the
|
||||||
|
<a
|
||||||
|
class="term"
|
||||||
|
href="#"
|
||||||
|
title=""
|
||||||
|
data-scope=""
|
||||||
|
data-format="dita"
|
||||||
|
data-type=""
|
||||||
|
target="_self"
|
||||||
|
>all_task_1</a
|
||||||
|
>
|
||||||
|
process repeatedly restarting.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-310472</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue on the web interface where checkboxes for
|
||||||
|
<span class="ph uicontrol">default information originate</span> and
|
||||||
|
ABR in OSPF NSSA configurations were automatically enabled which
|
||||||
|
resulted in unexpected configuration changes.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-308377</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
(<tt class="ph tt">PA-7050 firewalls in HA configurations only</tt>)
|
||||||
|
Fixed an issue where the firewall reached 100% disk utilization due to
|
||||||
|
the
|
||||||
|
<a
|
||||||
|
class="term"
|
||||||
|
href="#"
|
||||||
|
title=""
|
||||||
|
data-scope=""
|
||||||
|
data-format="dita"
|
||||||
|
data-type=""
|
||||||
|
target="_self"
|
||||||
|
>logrcvr</a
|
||||||
|
>
|
||||||
|
process repeatedly restarting and dumping core files due to a blocked
|
||||||
|
hints processing thread, which caused a failover.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-307714</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
(<tt class="ph tt">VM-Series firewalls only</tt>) Fixed an issue where
|
||||||
|
insufficient i-node space was available on the sysroot0 partition.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-302196</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where the dataplane stopped responding when cleaning up
|
||||||
|
expired sessions currently in Advanced Threat Prevention hold mode.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-277629</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where the firewall did not match the correct policy for
|
||||||
|
SSL forward decrypted HTTP/2 traffic when upgrading from PAN-OS
|
||||||
|
10.2.9-h1 to PAN-OS 11.2.3.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
@@ -0,0 +1,440 @@
|
|||||||
|
<table class="table colsep rowsep table-striped">
|
||||||
|
<!--cq:include script="../../common/tablestack.jsp" /-->
|
||||||
|
|
||||||
|
<colgroup>
|
||||||
|
<col style="width: 25.062656641604008%" />
|
||||||
|
<col style="width: 74.93734335839599%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead class="thead">
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<th class="entry">
|
||||||
|
<div class="p"><b class="ph b">Issue ID</b></div>
|
||||||
|
</th>
|
||||||
|
<th class="entry">
|
||||||
|
<div class="p"><b class="ph b">Description</b></div>
|
||||||
|
</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
|
||||||
|
<tbody class="tbody">
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">—</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">Fixes were made to address the following CVEs:</div>
|
||||||
|
<ul id="pan_os_11_1_13_h5_addressed_issues_ul-snk_4r1_gjc" class="ul">
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0265"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0265</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0264"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0264</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0263"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0263</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0262"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0262</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0261"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0261</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0258"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0258</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0257"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0257</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0256"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0256</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0259"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0259</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0300"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0300</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
</ul>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-323243</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where a
|
||||||
|
<a
|
||||||
|
class="term"
|
||||||
|
href="#"
|
||||||
|
title=""
|
||||||
|
data-scope=""
|
||||||
|
data-format="dita"
|
||||||
|
data-type=""
|
||||||
|
target="_self"
|
||||||
|
>configd</a
|
||||||
|
>
|
||||||
|
crash occurred when the
|
||||||
|
<span class="ph uicontrol">Policies > Security</span> view was
|
||||||
|
updated or refreshed in the web interface.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-318567</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where the OpenConfig plugin stopped working after a
|
||||||
|
configuration update.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-317583</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue with intermittent ICMP ping drops and packet loss in
|
||||||
|
traffic flows between a hub and branch after upgrading to an affected
|
||||||
|
PAN-OS release due to incorrect SD-WAN path monitor state.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-317466</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where SIP sessions stopped progressing after the
|
||||||
|
firewall received fragmented packets, fragmented at header field.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-317215</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
(<tt class="ph tt"
|
||||||
|
>VM-Series firewalls on ESXi with Intel E810 NICs using PCI
|
||||||
|
passthrough</tt
|
||||||
|
>) Fixed an issue where the
|
||||||
|
<a
|
||||||
|
class="term"
|
||||||
|
href="#"
|
||||||
|
title=""
|
||||||
|
data-scope=""
|
||||||
|
data-format="dita"
|
||||||
|
data-type=""
|
||||||
|
target="_self"
|
||||||
|
>brdagent</a
|
||||||
|
>
|
||||||
|
process became unresponsive during data port initialization, which
|
||||||
|
resulted in system instability, interface outages, HA split-brain
|
||||||
|
conditions, and unexpected reboots during failover.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-317177</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue on firewalls in DHCP Client mode where, after upgrading
|
||||||
|
to an affected release, the SNMP process unexpectedly restarted after
|
||||||
|
a commit, which led to false interface flap notifications on SNMP
|
||||||
|
managers.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b"> PAN-317155</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where the link status of log port 1 and log port 2 were
|
||||||
|
unable to be monitored via SNMP due to the OIDs for the individual
|
||||||
|
ports not being available.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-316631</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue BGP sessions experienced short disruptions across all
|
||||||
|
peers, interfaces, and slots when a multicast event persisted longer
|
||||||
|
than the NGP negotiated hold timers.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-314875</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
(<tt class="ph tt">PA-7500 firewalls only</tt>) Fixed an issue where
|
||||||
|
firewall logs were not visible in the Strata Logging Service even
|
||||||
|
though cloud logging was enabled and the firewall was successfully
|
||||||
|
forwarding logs.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-314435</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue on the Panorama web interface where custom application
|
||||||
|
tags for cloud applications were not consistently displayed in the
|
||||||
|
Application Filter or application details even though the tags were
|
||||||
|
configured via CLI and successfully enforced traffic blocking policy
|
||||||
|
rules.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-314126</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where session rematch did not properly apply updated
|
||||||
|
Security policy rules to existing traffic flows after committing
|
||||||
|
changes, which caused traffic to still be allowed when a new Security
|
||||||
|
policy was set to <span class="ph uicontrol">Deny</span>.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-313193</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
(<tt class="ph tt">Firewalls in Layer 2 mode only</tt>) Fixed an issue
|
||||||
|
where the new sessions were not able to be established due to the
|
||||||
|
firewall intermittently dropping valid MAC address entries for
|
||||||
|
specific VLANs when a manual switchover sent a high volume of traffic
|
||||||
|
to the firewall.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-311248</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where the ABR failed to translate and advertise the
|
||||||
|
default route (0.0.0.0/0) from an OSPF NSSA area into the OSPF
|
||||||
|
backbone area as a Type-5 LSA.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-310472</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue on the web interface where checkboxes for
|
||||||
|
<span class="ph uicontrol">default information originate</span> and
|
||||||
|
ABR in OSPF NSSA configurations were automatically enabled which
|
||||||
|
resulted in unexpected configuration changes.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-308377</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
(<tt class="ph tt">PA-7050 firewalls in HA configurations only</tt>)
|
||||||
|
Fixed an issue where the firewall reached 100% disk utilization due to
|
||||||
|
the
|
||||||
|
<a
|
||||||
|
class="term"
|
||||||
|
href="#"
|
||||||
|
title=""
|
||||||
|
data-scope=""
|
||||||
|
data-format="dita"
|
||||||
|
data-type=""
|
||||||
|
target="_self"
|
||||||
|
>logrcvr</a
|
||||||
|
>
|
||||||
|
process repeatedly restarting and dumping core files due to a blocked
|
||||||
|
hints processing thread, which caused a failover.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-307714</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
(<tt class="ph tt">VM-Series firewalls only</tt>) Fixed an issue where
|
||||||
|
insufficient i-node space was available on the sysroot0 partition.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-295728</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where configuring an OSPFv2 NSSA area range caused
|
||||||
|
OSPF-learned routes to become unreachable due to the incorrect
|
||||||
|
installation of a discard route when the NSSA range prefix matched an
|
||||||
|
existing OSPF route.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-295309</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where OSPF session using MD5 authentication experienced
|
||||||
|
intermittent flapping due to out-of-order packet processing.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-277629</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where the firewall did not match the correct policy for
|
||||||
|
SSL forward decrypted HTTP/2 traffic when upgrading from PAN-OS
|
||||||
|
10.2.9-h1 to PAN-OS 11.2.3.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
@@ -0,0 +1,163 @@
|
|||||||
|
<table class="table colsep rowsep table-striped">
|
||||||
|
<!--cq:include script="../../common/tablestack.jsp" /-->
|
||||||
|
|
||||||
|
<colgroup>
|
||||||
|
<col style="width: 25.062656641604008%" />
|
||||||
|
<col style="width: 74.93734335839599%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead class="thead">
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<th class="entry">
|
||||||
|
<div class="p"><b class="ph b">Issue ID</b></div>
|
||||||
|
</th>
|
||||||
|
<th class="entry">
|
||||||
|
<div class="p"><b class="ph b">Description</b></div>
|
||||||
|
</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
|
||||||
|
<tbody class="tbody">
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">—</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">Fixes were made to address the following CVEs:</div>
|
||||||
|
<ul id="pan_os_11_1_4_h33_addressed_issues_ul-snk_4r1_gjc" class="ul">
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0265"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0265</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0264"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0264</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0263"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0263</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0262"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0262</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0261"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0261</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0258"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0258</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0257"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0257</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0256"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0256</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0259"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0259</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0300"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0300</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
</ul>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-265399 </b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where DNS queries for uppercase internal domain (SRV
|
||||||
|
record) timed out when DNS Security was enabled.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
@@ -0,0 +1,286 @@
|
|||||||
|
<table class="table colsep rowsep table-striped">
|
||||||
|
<!--cq:include script="../../common/tablestack.jsp" /-->
|
||||||
|
|
||||||
|
<colgroup>
|
||||||
|
<col style="width: 25.062656641604008%" />
|
||||||
|
<col style="width: 74.93734335839599%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead class="thead">
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<th class="entry">
|
||||||
|
<div class="p"><b class="ph b">Issue ID</b></div>
|
||||||
|
</th>
|
||||||
|
<th class="entry">
|
||||||
|
<div class="p"><b class="ph b">Description</b></div>
|
||||||
|
</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
|
||||||
|
<tbody class="tbody">
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">—</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">Fixes were made to address the following CVEs:</div>
|
||||||
|
<ul id="pan_os_11_1_13_h5_addressed_issues_ul-snk_4r1_gjc" class="ul">
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0265"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0265</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0264"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0264</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0263"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0263</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0262"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0262</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0261"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0261</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0258"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0258</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0257"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0257</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0256"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0256</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0259"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0259</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0300"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0300</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
</ul>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-323243</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where a
|
||||||
|
<a
|
||||||
|
class="term"
|
||||||
|
href="#"
|
||||||
|
title=""
|
||||||
|
data-scope=""
|
||||||
|
data-format="dita"
|
||||||
|
data-type=""
|
||||||
|
target="_self"
|
||||||
|
>configd</a
|
||||||
|
>
|
||||||
|
crash occurred when the
|
||||||
|
<span class="ph uicontrol">Policies > Security</span> view was
|
||||||
|
updated or refreshed in the web interface.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-322281</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
(<tt class="ph tt">Firewalls in HA configurations only</tt>) Fixed an
|
||||||
|
issue where the HA 2 interface did not come up on the passive
|
||||||
|
firewall, which resulted in the firewall being unable to join the HA
|
||||||
|
pair.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-314126</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where session rematch did not properly apply updated
|
||||||
|
Security policy rules to existing traffic flows after committing
|
||||||
|
changes, which caused traffic to still be allowed when a new Security
|
||||||
|
policy was set to <span class="ph uicontrol">Deny</span>.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-311166</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where the firewall rebooted unexpectedly to the
|
||||||
|
<a
|
||||||
|
class="term"
|
||||||
|
href="#"
|
||||||
|
title=""
|
||||||
|
data-scope=""
|
||||||
|
data-format="dita"
|
||||||
|
data-type=""
|
||||||
|
target="_self"
|
||||||
|
>all_task_1</a
|
||||||
|
>
|
||||||
|
process repeatedly restarting.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-308377</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
(<tt class="ph tt">PA-7050 firewalls in HA configurations only</tt>)
|
||||||
|
Fixed an issue where the firewall reached 100% disk utilization due to
|
||||||
|
the
|
||||||
|
<a
|
||||||
|
class="term"
|
||||||
|
href="#"
|
||||||
|
title=""
|
||||||
|
data-scope=""
|
||||||
|
data-format="dita"
|
||||||
|
data-type=""
|
||||||
|
target="_self"
|
||||||
|
>logrcvr</a
|
||||||
|
>
|
||||||
|
process repeatedly restarting and dumping core files due to a blocked
|
||||||
|
hints processing thread, which caused a failover.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-307901 </b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where a leak in decryption counters caused resource
|
||||||
|
exhaustion, which led to a GlobalProtect service outage.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-307714</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
(<tt class="ph tt">VM-Series firewalls only</tt>) Fixed an issue where
|
||||||
|
insufficient i-node space was available on the sysroot0 partition.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-302196</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where the dataplane stopped responding when cleaning up
|
||||||
|
expired sessions currently in Advanced Threat Prevention hold mode.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
@@ -0,0 +1,29 @@
|
|||||||
|
<table class="table colsep rowsep table-striped">
|
||||||
|
<!--cq:include script="../../common/tablestack.jsp" /-->
|
||||||
|
|
||||||
|
<colgroup>
|
||||||
|
<col style="width: 25.062656641604008%" />
|
||||||
|
<col style="width: 74.93734335839599%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead class="thead">
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<th class="entry">
|
||||||
|
<div class="p"><b class="ph b">Issue ID</b></div>
|
||||||
|
</th>
|
||||||
|
<th class="entry">
|
||||||
|
<div class="p"><b class="ph b">Description</b></div>
|
||||||
|
</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
|
||||||
|
<tbody class="tbody">
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">—</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">This hotfix includes performance and bug fixes.</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
@@ -0,0 +1,321 @@
|
|||||||
|
<table class="table colsep rowsep table-striped">
|
||||||
|
<!--cq:include script="../../common/tablestack.jsp" /-->
|
||||||
|
|
||||||
|
<colgroup>
|
||||||
|
<col style="width: 25.062656641604008%" />
|
||||||
|
<col style="width: 74.93734335839599%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead class="thead">
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<th class="entry">
|
||||||
|
<div class="p"><b class="ph b">Issue ID</b></div>
|
||||||
|
</th>
|
||||||
|
<th class="entry">
|
||||||
|
<div class="p"><b class="ph b">Description</b></div>
|
||||||
|
</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
|
||||||
|
<tbody class="tbody">
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">—</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">Fixes were made to address the following CVEs:</div>
|
||||||
|
<ul id="pan_os_11_2_10_h6_addressed_issues_ul-snk_4r1_gjc" class="ul">
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0265"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0265</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0264"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0264</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0263"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0263</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0262"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0262</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0261"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0261</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0258"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0258</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0256"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0256</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0259"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0259</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0300"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0300</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
</ul>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-317215</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
(<tt class="ph tt"
|
||||||
|
>VM-Series firewalls on ESXi with Intel E810 NICs using PCI
|
||||||
|
passthrough</tt
|
||||||
|
>) Fixed an issue where the
|
||||||
|
<a
|
||||||
|
class="term"
|
||||||
|
href="#"
|
||||||
|
title=""
|
||||||
|
data-scope=""
|
||||||
|
data-format="dita"
|
||||||
|
data-type=""
|
||||||
|
target="_self"
|
||||||
|
>brdagent</a
|
||||||
|
>
|
||||||
|
process became unresponsive during data port initialization, which
|
||||||
|
resulted in system instability, interface outages, HA split-brain
|
||||||
|
conditions, and unexpected reboots during failover.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-315919</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where GlobalProtect pre-logon tunnel session was not
|
||||||
|
cleared even after the user was logged in. With this fix, the session
|
||||||
|
is cleared after the session timeout expires.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-313849</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue on Panorama where the
|
||||||
|
<a
|
||||||
|
class="term"
|
||||||
|
href="#"
|
||||||
|
title=""
|
||||||
|
data-scope=""
|
||||||
|
data-format="dita"
|
||||||
|
data-type=""
|
||||||
|
target="_self"
|
||||||
|
>logd</a
|
||||||
|
>
|
||||||
|
process exited unexpectedly when handling syslog forwarding.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-311192</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where the
|
||||||
|
<a
|
||||||
|
class="term"
|
||||||
|
href="#"
|
||||||
|
title=""
|
||||||
|
data-scope=""
|
||||||
|
data-format="dita"
|
||||||
|
data-type=""
|
||||||
|
target="_self"
|
||||||
|
>device-telemetry collect-now</a
|
||||||
|
>
|
||||||
|
process became unresponsive when the process was initiated multiple
|
||||||
|
times with other processes running concurrently, which prevented
|
||||||
|
subsequent telemetry collection.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-308377</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
(<tt class="ph tt">PA-7050 firewalls in HA configurations only</tt>)
|
||||||
|
Fixed an issue where the firewall reached 100% disk utilization due to
|
||||||
|
the
|
||||||
|
<a
|
||||||
|
class="term"
|
||||||
|
href="#"
|
||||||
|
title=""
|
||||||
|
data-scope=""
|
||||||
|
data-format="dita"
|
||||||
|
data-type=""
|
||||||
|
target="_self"
|
||||||
|
>logrcvr</a
|
||||||
|
>
|
||||||
|
process repeatedly restarting and dumping core files due to a blocked
|
||||||
|
hints processing thread, which caused a failover.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-306356</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where the
|
||||||
|
<a
|
||||||
|
class="term"
|
||||||
|
href="#"
|
||||||
|
title=""
|
||||||
|
data-scope=""
|
||||||
|
data-format="dita"
|
||||||
|
data-type=""
|
||||||
|
target="_self"
|
||||||
|
>logrcvr</a
|
||||||
|
>
|
||||||
|
process on a firewall stopped responding due to a document node being
|
||||||
|
unexpectedly freed.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-303663</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue on the firewall where SolarWinds monitoring systems
|
||||||
|
reported 100% usage for Slot1 Data Processor-0 Hardware Packet Buffers
|
||||||
|
due to an inaccurate reported packet buffer.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-295806</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where memory leaks on the
|
||||||
|
<a
|
||||||
|
class="term"
|
||||||
|
href="#"
|
||||||
|
title=""
|
||||||
|
data-scope=""
|
||||||
|
data-format="dita"
|
||||||
|
data-type=""
|
||||||
|
target="_self"
|
||||||
|
>configd</a
|
||||||
|
>
|
||||||
|
process occurred due to a hash insert operation failing during
|
||||||
|
connection management and SSL connections.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-288175</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Addressed a stack buffer overflow memory leak under plugin management
|
||||||
|
code path.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
File diff suppressed because it is too large
Load Diff
@@ -0,0 +1,308 @@
|
|||||||
|
<table class="table colsep rowsep table-striped">
|
||||||
|
<!--cq:include script="../../common/tablestack.jsp" /-->
|
||||||
|
|
||||||
|
<colgroup>
|
||||||
|
<col style="width: 25.062656641604008%" />
|
||||||
|
<col style="width: 74.93734335839599%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead class="thead">
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<th class="entry">
|
||||||
|
<div class="p"><b class="ph b">Issue ID</b></div>
|
||||||
|
</th>
|
||||||
|
<th class="entry">
|
||||||
|
<div class="p"><b class="ph b">Description</b></div>
|
||||||
|
</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
|
||||||
|
<tbody class="tbody">
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">—</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">Fixes were made to address the following CVEs:</div>
|
||||||
|
<ul id="pan_os_11_2_7_h13_addressed_issues_ul-snk_4r1_gjc" class="ul">
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0265"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0265</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0264"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0264</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0263"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0263</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0262"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0262</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0261"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0261</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0258"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0258</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0256"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0256</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0259"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0259</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0300"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0300</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
</ul>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-317772</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Added a fix to improve performance in lossy network conditions.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-315965</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue to address TCP proxy fast recovery behavior to follow
|
||||||
|
RFC 5681.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-315919</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where GlobalProtect pre-logon tunnel session was not
|
||||||
|
cleared even after the user was logged in. With this fix, the session
|
||||||
|
is cleared after the session timeout expires.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-311192</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where the
|
||||||
|
<a
|
||||||
|
class="term"
|
||||||
|
href="#"
|
||||||
|
title=""
|
||||||
|
data-scope=""
|
||||||
|
data-format="dita"
|
||||||
|
data-type=""
|
||||||
|
target="_self"
|
||||||
|
>device-telemetry collect-now</a
|
||||||
|
>
|
||||||
|
process became unresponsive when the process was initiated multiple
|
||||||
|
times with other processes running concurrently, which prevented
|
||||||
|
subsequent telemetry collection.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-308377</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
(<tt class="ph tt">PA-7050 firewalls in HA configurations only</tt>)
|
||||||
|
Fixed an issue where the firewall reached 100% disk utilization due to
|
||||||
|
the
|
||||||
|
<a
|
||||||
|
class="term"
|
||||||
|
href="#"
|
||||||
|
title=""
|
||||||
|
data-scope=""
|
||||||
|
data-format="dita"
|
||||||
|
data-type=""
|
||||||
|
target="_self"
|
||||||
|
>logrcvr</a
|
||||||
|
>
|
||||||
|
process repeatedly restarting and dumping core files due to a blocked
|
||||||
|
hints processing thread, which caused a failover.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-306356</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where the
|
||||||
|
<a
|
||||||
|
class="term"
|
||||||
|
href="#"
|
||||||
|
title=""
|
||||||
|
data-scope=""
|
||||||
|
data-format="dita"
|
||||||
|
data-type=""
|
||||||
|
target="_self"
|
||||||
|
>logrcvr</a
|
||||||
|
>
|
||||||
|
process on a firewall stopped responding due to a document node being
|
||||||
|
unexpectedly freed.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-303663</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue on the firewall where SolarWinds monitoring systems
|
||||||
|
reported 100% usage for Slot1 Data Processor-0 Hardware Packet Buffers
|
||||||
|
due to an inaccurate reported packet buffer.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-295806</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where memory leaks on the
|
||||||
|
<a
|
||||||
|
class="term"
|
||||||
|
href="#"
|
||||||
|
title=""
|
||||||
|
data-scope=""
|
||||||
|
data-format="dita"
|
||||||
|
data-type=""
|
||||||
|
target="_self"
|
||||||
|
>configd</a
|
||||||
|
>
|
||||||
|
process occurred due to a hash insert operation failing during
|
||||||
|
connection management and SSL connections.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-288175</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Addressed a stack buffer overflow memory leak under plugin management
|
||||||
|
code path.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">PAN-251024</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
Fixed an issue where GlobalProtect logs did not show the correct
|
||||||
|
region for the IP address due to content updates not retrieving the
|
||||||
|
latest configuration.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
@@ -0,0 +1,41 @@
|
|||||||
|
<table class="table colsep rowsep table-striped">
|
||||||
|
<!--cq:include script="../../common/tablestack.jsp" /-->
|
||||||
|
|
||||||
|
<colgroup>
|
||||||
|
<col style="width: 25.062656641604008%" />
|
||||||
|
<col style="width: 74.93734335839599%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead class="thead">
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<th class="entry">
|
||||||
|
<div class="p"><b class="ph b">Issue ID</b></div>
|
||||||
|
</th>
|
||||||
|
<th class="entry">
|
||||||
|
<div class="p"><b class="ph b">Description</b></div>
|
||||||
|
</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
|
||||||
|
<tbody class="tbody">
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">—</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">
|
||||||
|
A fix was made to address
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0257"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0257</a
|
||||||
|
>.
|
||||||
|
</div>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
@@ -0,0 +1,139 @@
|
|||||||
|
<table class="table colsep rowsep table-striped">
|
||||||
|
<!--cq:include script="../../common/tablestack.jsp" /-->
|
||||||
|
|
||||||
|
<colgroup>
|
||||||
|
<col style="width: 25%" />
|
||||||
|
<col style="width: 75%" />
|
||||||
|
</colgroup>
|
||||||
|
<thead class="thead">
|
||||||
|
<tr class="row rowsep">
|
||||||
|
<th class="entry">
|
||||||
|
<div class="p"><b class="ph b">Issue ID</b></div>
|
||||||
|
</th>
|
||||||
|
<th class="entry">
|
||||||
|
<div class="p"><b class="ph b">Description</b></div>
|
||||||
|
</th>
|
||||||
|
</tr>
|
||||||
|
</thead>
|
||||||
|
|
||||||
|
<tbody class="tbody">
|
||||||
|
<tr class="row">
|
||||||
|
<td class="entry">
|
||||||
|
<div class="p"><b class="ph b">—</b></div>
|
||||||
|
</td>
|
||||||
|
<td class="entry relcol">
|
||||||
|
<div class="p">Fixes were made to address the following CVEs:</div>
|
||||||
|
<ul id="panos-addressed-issues-12.1.3_ul-snk_4r1_gjc" class="ul">
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0265"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0265</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0264"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0264</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0263"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0263</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0262"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0262</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0261"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0261</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0258"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0258</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0257"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0257</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0256"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0256</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
<li class="li">
|
||||||
|
<a
|
||||||
|
class="xref"
|
||||||
|
href="https://security.paloaltonetworks.com/CVE-2026-0259"
|
||||||
|
title=""
|
||||||
|
data-scope="external"
|
||||||
|
data-format="html"
|
||||||
|
data-type=""
|
||||||
|
target="_blank"
|
||||||
|
>CVE-2026-0259</a
|
||||||
|
>
|
||||||
|
</li>
|
||||||
|
</ul>
|
||||||
|
</td>
|
||||||
|
</tr>
|
||||||
|
</tbody>
|
||||||
|
</table>
|
||||||
@@ -0,0 +1,17 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.10-h30
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-301222
|
||||||
|
|
||||||
|
Fixed an issue where DNS Security logs incorrectly displayed a sinkhole action for benign DNS categories due to the firewall saving the drop or sinkhole action in session flags without discarding the session.
|
||||||
|
|
||||||
|
## PAN-291653
|
||||||
|
|
||||||
|
Fixed an issue where the GlobalProtect host ID field was intermittently blank in traffic logs on Prisma Access, even when the user was connected and had the correct host ID information. This occurred when the IP address to host ID entry expired and the entry was re-inserted without the dataplane flag being set.
|
||||||
|
|
||||||
|
## PAN-195264
|
||||||
|
|
||||||
|
Fixed an issue where the login lifetime countdown timer reset when using an authentication override cookie to log in to the gateway.
|
||||||
@@ -0,0 +1,9 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.10-h31
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-312703
|
||||||
|
|
||||||
|
Fixed an issue where failures between useridd and logrcvr processes could lead to intermittent loss of User-ID and HIP Match logs during log spikes.
|
||||||
@@ -0,0 +1,19 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.10-h36
|
||||||
|
---
|
||||||
|
|
||||||
|
## BLANK-000000
|
||||||
|
|
||||||
|
Fixes were made to address the following CVEs:
|
||||||
|
|
||||||
|
- [CVE-2026-0265](https://security.paloaltonetworks.com/CVE-2026-0265)
|
||||||
|
- [CVE-2026-0264](https://security.paloaltonetworks.com/CVE-2026-0264)
|
||||||
|
- [CVE-2026-0262](https://security.paloaltonetworks.com/CVE-2026-0262)
|
||||||
|
- [CVE-2026-0261](https://security.paloaltonetworks.com/CVE-2026-0261)
|
||||||
|
- [CVE-2026-0258](https://security.paloaltonetworks.com/CVE-2026-0258)
|
||||||
|
- [CVE-2026-0257](https://security.paloaltonetworks.com/CVE-2026-0257)
|
||||||
|
- [CVE-2026-0256](https://security.paloaltonetworks.com/CVE-2026-0256)
|
||||||
|
- [CVE-2026-0259](https://security.paloaltonetworks.com/CVE-2026-0259)
|
||||||
|
- [CVE-2026-0300](https://security.paloaltonetworks.com/CVE-2026-0300)
|
||||||
@@ -2,8 +2,6 @@
|
|||||||
type: Addressed
|
type: Addressed
|
||||||
product: PAN-OS
|
product: PAN-OS
|
||||||
version: 10.2.18-h1
|
version: 10.2.18-h1
|
||||||
source: common-crawl
|
|
||||||
crawl: CC-MAIN-2026-12
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## PAN-306502
|
## PAN-306502
|
||||||
|
|||||||
@@ -0,0 +1,19 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 10.2.18-h6
|
||||||
|
---
|
||||||
|
|
||||||
|
## BLANK-000000
|
||||||
|
|
||||||
|
Fixes were made to address the following CVEs:
|
||||||
|
|
||||||
|
- [CVE-2026-0265](https://security.paloaltonetworks.com/CVE-2026-0265)
|
||||||
|
- [CVE-2026-0264](https://security.paloaltonetworks.com/CVE-2026-0264)
|
||||||
|
- [CVE-2026-0262](https://security.paloaltonetworks.com/CVE-2026-0262)
|
||||||
|
- [CVE-2026-0261](https://security.paloaltonetworks.com/CVE-2026-0261)
|
||||||
|
- [CVE-2026-0258](https://security.paloaltonetworks.com/CVE-2026-0258)
|
||||||
|
- [CVE-2026-0257](https://security.paloaltonetworks.com/CVE-2026-0257)
|
||||||
|
- [CVE-2026-0256](https://security.paloaltonetworks.com/CVE-2026-0256)
|
||||||
|
- [CVE-2026-0259](https://security.paloaltonetworks.com/CVE-2026-0259)
|
||||||
|
- [CVE-2026-0300](https://security.paloaltonetworks.com/CVE-2026-0300)
|
||||||
@@ -2,356 +2,99 @@
|
|||||||
type: Addressed
|
type: Addressed
|
||||||
product: PAN-OS
|
product: PAN-OS
|
||||||
version: 10.2.18
|
version: 10.2.18
|
||||||
source: common-crawl
|
|
||||||
crawl: CC-MAIN-2026-12
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## WF500-5854
|
## PAN-303559
|
||||||
|
|
||||||
The WildFire analysis report on the firewall log viewer (**Monitoring** > **WildFire Submissions**) does not display the following data fields: File Type, SHA-256, MD-5, and File Size".
|
Fixed an issue where, after manuallly creating a device telemetry bundle, the hour_cli_output.txt file within the bundle had a file size of 0 bytes. This occurred when checking the bundle content after enabling device telemetry and setting the device telemetry upload endpoint.
|
||||||
|
|
||||||
**Workaround**: Download and open the WildFire analysis report in the PDF format using the link in the upper right-hand corner of the **Detailed Log View**.
|
## PAN-301018
|
||||||
|
|
||||||
## WF500-5843
|
Fixed an issue on Panorama where API queries for correlated category logs incorrectly returned a count of 0.
|
||||||
|
|
||||||
In a WildFire appliance cluster, issuing the show cluster-all peers CLI command when a node within the cluster is being rebooted generates the following error: Server error : An error occured.
|
## PAN-300055
|
||||||
|
|
||||||
## WF500-5840
|
Fixed an issue where the firewall experienced high disk utilization in the /opt/pancfg/mgmt/content-preview directory due to older content data not being automatically removed when an error occurred during the process.
|
||||||
|
|
||||||
The sample analysis statistics that are returned when issuing the show wildfire local statistics CLI command in WildFire appliance cluster deployments may not accurately reflect the number of samples that have been processed.
|
## PAN-297775
|
||||||
|
|
||||||
## WF500-5823
|
Fixed an issue where, after upgrading to an affected PAN-OS release, the Visible Virtual System field referenced the vsys name instead of the vsys ID, which caused inter-vsys routing to fail. This occurred when a vsys display name matched one of the vsys IDs. If you're using a multivsys environment, you must upgrade your firewalls to a fixed PAN-OS version. The best practice is to upgrade both the firewalls and Panorama to a fixed PAN-OS version.
|
||||||
|
|
||||||
The following WildFire appliance CLI command does not return a signature generation status as expected: show wildfire global signature-status. This does not corrupt or otherwise prevent the WildFire appliance from analyzing a sample.
|
- If you don't upgrade Panorama to a fixed version, you'll encounter PAN-245064, where a commit on a multivsys firewall fails with the message vsys name should end with a number vsys is invalid after you **Export or push device config bundle** from 11.1.1 Panorama.
|
||||||
|
- After you upgrade Panorama to a fixed version, you'll encounter PAN-214177, which causes an **Export or Push device config bundle** from Panorama to the firewall to fail. The workaround for PAN-214177 is to first push only the template configuration and then push the device group configurations.
|
||||||
|
|
||||||
## WF500-5781
|
## PAN-297708
|
||||||
|
|
||||||
The WildFire appliance might erroneously generate and log the following device certification error: Device certificate is missing or invalid. It cannot be renewed.
|
Fixed an issue where a long-lived session with many Machine Learning (ML) model triggers caused a memory leak of feature states associated with the ML model runs. This resulted in Spyware_State failure increases, allocation max outs, and impaired policy matching.
|
||||||
|
|
||||||
## WF500-5754
|
## PAN-297609
|
||||||
|
|
||||||
In WildFire appliance clusters, issuing the show cluster controller CLI command generates an error when an IPv6 address is configured for the management interface but not for the cluster interface.
|
Fixed an issue where the the CLI command debug user-id refresh user-id agent all failed with the error message Invalid agent name. Agent name should be 1 to 31 characters long.
|
||||||
|
|
||||||
**Workaround:** Ensure all WildFire appliance interfaces that are enabled use matching protocols (all IPv4 or all IPv6).
|
## PAN-297261
|
||||||
|
|
||||||
## WF500-5632
|
Fixed an issue where the proxy-protocol debug level was set to verbose on Prisma Access instances, even when it was not explicitly configured, which caused excessive logging by the pan_task process.
|
||||||
|
|
||||||
The number of registered WildFire appliances reported in Panorama (**Panorama** > **Managed WildFire Appliances** > **Firewalls Connected** > **View**) does not accurately reflect the current status of connected WildFire appliances.
|
## PAN-295095
|
||||||
|
|
||||||
## PAN-303959
|
Fixed an issue where, when you used a syslog forwarding profile with the CEF format, an additional string was appended to the end of the log message when viewing the log entry from the Universal Forwarder directory.
|
||||||
|
|
||||||
Traffic that is incorrectly identified as unknown-tcp/unknown-udp eventually drops due to an App-ID resource limitation issue.
|
## PAN-295049
|
||||||
|
|
||||||
## PAN-297610
|
Fixed an issue where the logrcvr process stopped responding due to memory allocation errors during Redis communication.
|
||||||
|
|
||||||
A firewall may become unresponsive after an upgrade due to the fsck command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
## PAN-294893
|
||||||
|
|
||||||
## PAN-297295
|
Fixed an issue where firewalls with the **Send handshake messages to CTD for inspection** setting enabled caused incorrect security policy rules to be matched. Specifically, traffic not identified as openai-base or openai-chatgpt applications was incorrectly matched by the ALLOW-OPEN-AI-FULL-ACCESS-URLS-ALERTS rule. Additionally, the expected response page for blocked URLs was not displayed.
|
||||||
|
|
||||||
```caveat
|
## PAN-292447
|
||||||
VM-Series firewalls in Microsoft Azure environments only
|
|
||||||
```
|
|
||||||
|
|
||||||
After upgrading to an affected release, the firewall restarts continuously because the brdagent process restarts multiple times and exhausts its restart limit, resulting in a segfault error. This issue occurs when a high burst of traffic is sent to the Azure PA-VM (Palo Alto Networks Virtual Machine), and impacts production environments due to the regular reboots.
|
Fixed an issue where Panorama did not display data in the **Feature Adoption** tab in Strata Cloud Manager due to the system creating and deleting a CLI user for each interval instead of reusing a permanent CLI user for telemetry.
|
||||||
|
|
||||||
**Workaround:** Migrate the VM instance to Dv5 instance type. On these instance types, SYN packets are not routed to the synthetic path, avoiding this condition. Suggested direct resizing paths are:
|
## PAN-291172
|
||||||
|
|
||||||
- D3_v2/DS3_v2 to D8ds_v5
|
Fixed an issue where administrators were unable to gather path monitoring failure information when troubleshooting high dataplane CPU utilization.
|
||||||
- D4_v2/DS4_v2 to D8ds_v5
|
|
||||||
- D5_v2/DS5_v2 to D16ds_v5
|
|
||||||
|
|
||||||
Azure VMs with ephemeral storage can only be resized to another type with ephemeral storage.
|
## PAN-290665
|
||||||
|
|
||||||
## PAN-295255
|
Fixed an issue with firewalls enabled with Security profiles where certain traffic conditions caused high dataplane CPU utilization and packet buffer exhaustion, which caused LACP flapping conditions.
|
||||||
|
|
||||||
Palo Alto Networks next-generation firewalls may experience service disruptions due to all_task process crashes when deployed in environments having non-uniform MTU and are terminating IPSec tunnels.
|
## PAN-289067
|
||||||
|
|
||||||
## PAN-284067
|
Fixed an issue where, after upgrading Panorama in a High Availability (HA) pair, the configuration logs stopped synchronizing from the primary Panorama to the secondary Panorama. This issue occurred because the log forwarding flag was permanently disabled due to the connection state not being active when the log-fwd-ctrl message was received.
|
||||||
|
|
||||||
A cumulative memory leak in the devsrvr process gets progressively worse whenever the CLI command show running application statistics is issued. This memory leak will gradually consume system memory and produce an out-of-memory (OOM) condition, leading to an eventual firewall reboot.
|
## PAN-288097
|
||||||
|
|
||||||
**Workaround:** Avoid using the CLI command: show running application statistics.
|
Fixed an issue where on the firewall where the routed process stopped responding after changing the MTU or any link state parameters when OSPF and PIM were enabled on the same interface.
|
||||||
|
|
||||||
## PAN-281370
|
## PAN-287387
|
||||||
|
|
||||||
The Advanced WildFire Inline ML models **OOXML** and **Mach-O** erroneously display as being available from the CLI; however, they are only available on PAN-OS 11.1.3 and later releases.
|
Fixed an issue on Panorama where API jobs failed with the error message Server error: Timed out while getting config lock. This occurred due to slow set request performance when setting a large number of address objects in a single set call.
|
||||||
|
|
||||||
## PAN-266900
|
## PAN-285208
|
||||||
|
|
||||||
In Panorama, the **OK** button does not work when trying to install configurations to a managed firewall from the **Managed Devices** > **Summary** > **Install** section, even after selecting the update type and file from the drop-down menu and choosing the firewall.
|
Fixed an issue where the firewall did not automatically recover after a machine check exception (MCE) occurred.
|
||||||
|
|
||||||
## PAN-260851
|
## PAN-283237
|
||||||
|
|
||||||
From the NGFW or Panorama CLI, you can override the existing application tag even if Disable Override is enabled for the application (**Objects** > **Applications**) tag.
|
Fixed an issue where traffic logs incorrectly displayed the action as **allow** for traffic matching a Security policy rule configured with the action set to **deny**. This issue occurred due to the child session being used for policy rule lookup when a configuration update triggered a rematch if the FTP-data application was not in the rule.
|
||||||
|
|
||||||
## PAN-259769
|
## PAN-281588
|
||||||
|
|
||||||
GlobalProtect portal is not accessible via a web browser and the app displays the error ERR_EMPTY_RESPONSE.
|
Fixed an issue where packet buffer depletion occurred due to the a high number of tcp_pkt_queued packets when Jumbo was enabled.
|
||||||
|
|
||||||
## PAN-237106
|
## PAN-266843
|
||||||
|
|
||||||
LSVPN satellite certificates may be generated with serial numbers exceeding 40 hexadecimal characters. This causes certificate revocation and deletion operations to fail with the following error messages:
|
Fixed an issue on airgapped firewalls where cloud connection errors flooded the system logs.
|
||||||
|
|
||||||
- db-serialno can be at most 40 characters
|
## PAN-262353
|
||||||
- db-serialno is invalid
|
|
||||||
|
|
||||||
**Workaround:**
|
Fixed an issue where, when Panorama was upgraded to PAN-OS 10.2.10, and log collectors were on PAN-OS 10.2.9-h1, logs from a log collector group were not viewable on a Panorama.
|
||||||
|
|
||||||
To resolve this issue, use the following CLI commands with the LSVPN satellite serial number to manually delete or revoke the affected certificates:
|
## PAN-237349
|
||||||
|
|
||||||
**Delete certificate information**:delete sslmgr-store certificate-info portal name <name> serialno <satellite_serial>
|
Fixed an issue where URLs with over 965 characters were unable to be logged in the URL filtering log.
|
||||||
|
|
||||||
**Revoke satellite certificates**:delete sslmgr-store satellite-info-revoke-certificate portal <name> serialno <list_of_satellite_serials>
|
## PAN-233542
|
||||||
|
|
||||||
## PAN-234015
|
Fixed an issue where the firewall did not display the source address due to an uninitialized scalar variable.
|
||||||
|
|
||||||
The X-Forwarded-For (XFF) value is not displayed in traffic logs.
|
|
||||||
|
|
||||||
## PAN-223365
|
|
||||||
|
|
||||||
The Panorama management server is unable to query any logs if the ElasticSearch health status for any Log Collector (**Panorama** > **Managed Collector** is degraded.
|
|
||||||
|
|
||||||
**Workaround:** [Log in to the Log Collector CLI](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-cli) and restart ElasticSearch.
|
|
||||||
|
|
||||||
admin debug elasticsearch es-restart all
|
|
||||||
|
|
||||||
## PAN-229865
|
|
||||||
|
|
||||||
Upgrading a PA-220 firewall running a PAN-OS 10.1 release fails when the target PAN-OS upgrade version is PAN-OS 10.2.5.
|
|
||||||
|
|
||||||
**Workaround:** On your upgrade path to PAN-OS 10.2.5, first upgrade to PAN-OS 10.2.4 and then upgrade to PAN-OS 10.2.5.
|
|
||||||
|
|
||||||
## PAN-223677
|
|
||||||
|
|
||||||
```caveat
|
|
||||||
PA-3410, PA-3420, PA-3430, PA-3440, PA-5410, PA-5420, and PA-5430 firewalls
|
|
||||||
```
|
|
||||||
|
|
||||||
By enabling [Lockless QoS](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/quality-of-service/configure-lockless-qos) feature, a slight degradation in App-ID and Threat performance is expected.
|
|
||||||
|
|
||||||
## PAN-222586
|
|
||||||
|
|
||||||
On PA-5410, PA-5420, and PA-5430 firewalls, the Filter dropdown menus, Forward Methods, and Built-In Actions for Correlation Log settings (**Device** > **Log Settings**) are not displayed and cannot be configured.
|
|
||||||
|
|
||||||
## PAN-221775
|
|
||||||
|
|
||||||
A Malformed Request error is displayed when you **Test Connection** for an email server profile (**Device** > **Server Profiles** > **Email**) using **SMTP over TLS** and the Password includes an ampersand (&).
|
|
||||||
|
|
||||||
## PAN-213746
|
|
||||||
|
|
||||||
On the Panorama management server, the **Hostkey** displayed as undefined undefined if you override an SSH Service Profile (**Device** > **Certificate Management** > **SSH Service Profile**) Hostkey configured in a Template from the Template Stack.
|
|
||||||
|
|
||||||
## PAN-213119
|
|
||||||
|
|
||||||
PA-5410 and PA-5420 firewalls display the following error when you view the Block IP list (**Monitor** > **Block IP**):
|
|
||||||
|
|
||||||
show -> dis-block-table is unexpected
|
|
||||||
|
|
||||||
## PAN-212889
|
|
||||||
|
|
||||||
On the Panorama management server, different threat names are used when querying the same threat in the Threat Monitor (**Monitor** > **App Scope** > **Threat Monitor**) and **ACC**. This results in the ACC displaying no data to display when you are redirected to the ACC after clicking a threat name in the Threat Monitor and filtering the same threat name in the Global Filters.
|
|
||||||
|
|
||||||
## PAN-212533
|
|
||||||
|
|
||||||
Modifying the **Administrator Type** for an existing administrator (**Device** > **Administrators** or **Panorama** > **Administrators**) from Superuser to a **Role-Based** custom admin, or vice versa, does not modify the access privileges of the administrator.
|
|
||||||
|
|
||||||
## PAN-211531
|
|
||||||
|
|
||||||
On the Panorama management server, admins can still perform a selective push to managed firewalls when **Push All Changes** and **Push for Other Admins** are disabled in the admin role profile (**Panorama** > **Admin Roles**).
|
|
||||||
|
|
||||||
## PAN-209288
|
|
||||||
|
|
||||||
Certificates are not successfully generated using SCEP (**Device** > **Certificate Management** > **SCEP**).
|
|
||||||
|
|
||||||
## PAN-208622
|
|
||||||
|
|
||||||
A file upload to Box.com exceeding 6 files gets stuck and fails to upload if you specify an Enterprise DLP data filtering profile (**Objects** > **DLP** > **Data Filtering Profiles** with the Action set to Block to a Security policy rule (**Policies** > **Security**).
|
|
||||||
|
|
||||||
## PAN-204689
|
|
||||||
|
|
||||||
Upon upgrade to PAN-OS 10.2.4, the following GlobalProtect settings do not work:
|
|
||||||
|
|
||||||
- **Allow user to disconnect GlobalProtect App** > **Allow with Passcode**
|
|
||||||
- **Allow user to Disable GlobalProtect App** > **Allow with Passcode**
|
|
||||||
- **Allow User to Uninstall GlobalProtect App****Allow with Password**
|
|
||||||
|
|
||||||
## PAN-196758
|
|
||||||
|
|
||||||
On the Panorama management server, pushing a configuration change to firewalls leveraging SD-WAN erroneously show the auto-provisioned BGP configurations for SD-WAN as being edited or deleted despite no edits or deletions being made when you **Preview Changes** (**Commit** > **Push to Devices** > **Edit Selections** or **Commit** > **Commit and Push** > **Edit Selections**).
|
|
||||||
|
|
||||||
## PAN-196504
|
|
||||||
|
|
||||||
License deactivation fails for VM-Series firewalls licensed using PA-VM Bundle 3 (BND3).
|
|
||||||
|
|
||||||
## PAN-194996
|
|
||||||
|
|
||||||
When using a 10.2.2 Panorama to manage a Panorama Managed Prisma Access 3.1.2 deployment, allocating bandwidth for a remote network deployment fails (the OK button is grayed out).
|
|
||||||
|
|
||||||
**Workaround**: Retry the operation.
|
|
||||||
|
|
||||||
## PAN-194519
|
|
||||||
|
|
||||||
```caveat
|
|
||||||
PA-5450 firewall only
|
|
||||||
```
|
|
||||||
|
|
||||||
Trying to configure a custom payload format under **Device** > **Server Profiles** > **HTTP** yields a Javascript error.
|
|
||||||
|
|
||||||
## PAN-194515
|
|
||||||
|
|
||||||
```caveat
|
|
||||||
PA-5450 firewall only
|
|
||||||
```
|
|
||||||
|
|
||||||
The Panorama web interface does not display any predefined template stack variables in the dropdown menu under **Device** > **Setup** > **Log Interface** > **IP Address**.
|
|
||||||
|
|
||||||
**Workaround:** Configure the log interface IP address on the individual firewall web interface instead of on Panorama.
|
|
||||||
|
|
||||||
## PAN-194424
|
|
||||||
|
|
||||||
```caveat
|
|
||||||
PA-5450 firewall only
|
|
||||||
```
|
|
||||||
|
|
||||||
Upgrading to PAN-OS 10.2.2 while having a log interface configured can cause both the log interface and the management interface to remain connected to the log collector.
|
|
||||||
|
|
||||||
**Workaround:** Restart the log receiver service by running the following CLI command:
|
|
||||||
|
|
||||||
debug software restart process log-receiver
|
|
||||||
|
|
||||||
## PAN-194202
|
|
||||||
|
|
||||||
```caveat
|
|
||||||
PA-5450 firewall only
|
|
||||||
```
|
|
||||||
|
|
||||||
If the management interface and logging interface are configured on the same subnetwork, the firewall conducts log forwarding using the management interface instead of the logging interface.
|
|
||||||
|
|
||||||
## PAN-190727
|
|
||||||
|
|
||||||
```caveat
|
|
||||||
PA-5450 firewall only
|
|
||||||
```
|
|
||||||
|
|
||||||
Documentation for configuring the log interface is unavailable on the web interface and in the PAN-OS Administrator’s Guide.
|
|
||||||
|
|
||||||
## PAN-189111
|
|
||||||
|
|
||||||
After deleting an MP pod and it comes up, the show routing command output appears empty and traffic stops working.
|
|
||||||
|
|
||||||
## PAN-189076
|
|
||||||
|
|
||||||
On a firewall with Advanced Routing enabled, OSPFv3 peers using a broadcast link and a designated router (DR) priority of 0 (zero) are stuck in a two-way state after HA failover.
|
|
||||||
|
|
||||||
**Workaround:** Configure at least one OSPFv3 neighbor with a non-zero priority setting in the same broadcast domain.
|
|
||||||
|
|
||||||
## PAN-188358
|
|
||||||
|
|
||||||
After triggering a soft reboot on a M-700 appliance, the Management port LEDs do not light up when a 10G Ethernet cable is plugged in.
|
|
||||||
|
|
||||||
## PAN-187685
|
|
||||||
|
|
||||||
On the Panorama management server, the Template Status displays no synchronization status (**Panorama** > **Managed Devices** > **Summary**) after a bootstrapped firewall is successfully added to Panorama.
|
|
||||||
|
|
||||||
**Workaround:** After the bootstrapped firewall is successfully added to Panorama, [log in to the Panorama web interface](https://docs.paloaltonetworks.com/panorama/10-2/panorama-admin/set-up-panorama/access-and-navigate-panorama-management-interfaces/log-in-to-the-panorama-web-interface.html) and select **Commit** > **Push to Devices**.
|
|
||||||
|
|
||||||
## PAN-187643
|
|
||||||
|
|
||||||
If you enable SCTP security using a Panorama template when **SCTP INIT Flood Protection** is enabled in the Zone Protection profile using Panorama and you commit all changes, the commit is successful but the **SCTP INIT** option is not available in the Zone Protection profile.
|
|
||||||
|
|
||||||
**Workaround:** Log out of the firewall and log in again to make the **SCIT INIT** option available on the web interface.
|
|
||||||
|
|
||||||
## PAN-187612
|
|
||||||
|
|
||||||
On the Panorama management server, not all data profiles (**Objects** > **DLP Data Filtering Profiles**) are displayed after you:
|
|
||||||
|
|
||||||
- Upgrade Panorama to PAN-OS 10.2 and upgrade the Enterprise DLP plugin to version 3.0.
|
|
||||||
- Downgrade Panorama to PAN-OS 10.1 and downgrade the Enterprise DLP plugin to version 1.0.
|
|
||||||
|
|
||||||
**Workaround:** Log in to the Panorama CLI and reset the DLP plugin.
|
|
||||||
|
|
||||||
admin > request plugins dlp reset.
|
|
||||||
|
|
||||||
## PAN-187407
|
|
||||||
|
|
||||||
The configured Advanced Threat Prevention inline cloud analysis action for a given model might not be honored under the following condition: If the firewall is set to **Hold client request for category lookup**and the action set to **Reset-Both** and the URL cache has been cleared, the first request for inline cloud analysis will be bypassed.
|
|
||||||
|
|
||||||
## PAN-187370
|
|
||||||
|
|
||||||
On a firewall with Advanced Routing enabled, if there is also a logical router instance that uses the default configuration and has no interfaces assigned to it, this will result in terminating the management daemon and main routing daemon in the firewall during commit.
|
|
||||||
|
|
||||||
**Workaround**: Do not use a logical router instance with no interfaces bound to it.
|
|
||||||
|
|
||||||
## PAN-186283
|
|
||||||
|
|
||||||
Templates appear out-of-sync on Panorama after successfully deploying the CFT stack using the Panorama plugin for AWS.
|
|
||||||
|
|
||||||
**Workaround**: Use **Commit** > **Push to Devices** to synchronize the templates.
|
|
||||||
|
|
||||||
## PAN-186282
|
|
||||||
|
|
||||||
On HA deployments on AWS and Azure, Panorama fails to populate match criteria automatically when adding dynamic address groups.
|
|
||||||
|
|
||||||
**Workaround:** Reboot the Panorama HA pair.
|
|
||||||
|
|
||||||
## PAN-184406
|
|
||||||
|
|
||||||
Using the CLI to add a RAID disk pair to an M-700 appliance causes the dmdb process to crash.
|
|
||||||
|
|
||||||
**Workaround:** Contact customer support to stop the dmdb process before adding a RAID disk pair to a M-700 appliance.
|
|
||||||
|
|
||||||
## PAN-183404
|
|
||||||
|
|
||||||
Static IP addresses are not recognized when "and" operators are used with IP CIDR range.
|
|
||||||
|
|
||||||
## PAN-181933
|
|
||||||
|
|
||||||
If you use multiple log forwarding cards (LFCs) on the PA-7000 series, all of the cards may not receive all of the updates and the mappings for the clients may become out of sync, which causes the firewall to not correctly populate the Source User column in the session logs.
|
|
||||||
|
|
||||||
## PAN-181823
|
|
||||||
|
|
||||||
On a PA-5400 Series firewall (minus the PA-5450), setting the peer port to forced 10M or 100M speed causes any multi-gigabit RJ-45 ports on the firewall to go down if they are set to Auto.
|
|
||||||
|
|
||||||
## PAN-180661
|
|
||||||
|
|
||||||
On the Panorama management server, pushing an unsupported Minimum Password Complexity (**Device** > **Setup** > **Management**) to a managed firewall erroneously displays commit time out as the reason the commit failed.
|
|
||||||
|
|
||||||
## PAN-180104
|
|
||||||
|
|
||||||
When upgrading a CN-Series as a DaemonSet deployment to PAN-OS 10.2, CN-NGFW pods fail to connect to CN-MGMT pod if the Kubernetes cluster previously had a CN-Series as a DaemonSet deployment running PAN-OS 10.0 or 10.1.
|
|
||||||
|
|
||||||
**Workaround**: Reboot the worker nodes before upgrading to PAN-OS 10.2.
|
|
||||||
|
|
||||||
## PAN-178194
|
|
||||||
|
|
||||||
A user interface issue in PAN-OS renders the contents of the **Inline ML** tab in the **URL Filtering Profile** inaccessible on firewalls licensed for Advanced URL Filtering. Additionally, a message indicating that a **License required for URL filtering to function** is unavailable displays at the bottom of the UI. These errors do not affect the operation of Advanced URL Filtering or URL Filtering Inline ML.
|
|
||||||
|
|
||||||
**Workaround:** Configuration settings for URL Filtering Inline ML must be applied through the CLI. The following configuration commands are available:
|
|
||||||
|
|
||||||
- Define URL exceptions for specific web sites—
|
|
||||||
admin#set profiles url-filtering <url_filtering_profile_name> mlav-category-exception
|
|
||||||
|
|
||||||
- Configuration settings for each inline ML model—
|
|
||||||
admin#set profiles url-filtering <url_filtering_profile_name> mlav-engine-urlbased-enabled
|
|
||||||
|
|
||||||
## PAN-177455
|
|
||||||
|
|
||||||
PAN-OS 10.2.0 is not supported on PA-7000 Series firewalls with HA (High Availability) clustering enabled and using an HA4 communication link. Attempting to load PAN-OS 10.2.0 on the firewall causes the PA-7000 100G NPC to go offline. As a result, the firewall fails to boot normally and enters maintenance mode. HA Pairs of Active-Passive and Active-Active firewalls are not affected.
|
|
||||||
|
|
||||||
## PAN-175915
|
|
||||||
|
|
||||||
When the firewall is deployed on N3 and N11 interfaces in 5G networks and 5G-HTTP/2 traffic inspection is enabled in the Mobile Network Protection Profile, the traffic logs do not display network slice SST and SD values.
|
|
||||||
|
|
||||||
## PAN-174982
|
|
||||||
|
|
||||||
In HA active/active configurations where, when interfaces that were associated with a virtual router were deleted, the configuration change did not sync.
|
|
||||||
|
|
||||||
## PAN-172274
|
|
||||||
|
|
||||||
When you activate the advanced URL filtering license, your license entitlements for PAN-DB and advanced URL filtering might not display correctly on the firewall — this is a display anomaly, not a licensing issue, and does not affect access to the services.
|
|
||||||
|
|
||||||
**Workaround:** Issue the following command to retrieve and update the licenses: license request fetch.
|
|
||||||
|
|
||||||
## PAN-171938
|
|
||||||
|
|
||||||
No results are displayed when you **Show Application Filter** for a Security policy rule (**Policies** > **Security** > **Application** > **Value** > **Show Application Filter**).
|
|
||||||
|
|||||||
@@ -0,0 +1,80 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 11.1.10-h25
|
||||||
|
---
|
||||||
|
|
||||||
|
## BLANK-000000
|
||||||
|
|
||||||
|
Fixes were made to address the following CVEs:
|
||||||
|
|
||||||
|
- [CVE-2026-0265](https://security.paloaltonetworks.com/CVE-2026-0265)
|
||||||
|
- [CVE-2026-0264](https://security.paloaltonetworks.com/CVE-2026-0264)
|
||||||
|
- [CVE-2026-0263](https://security.paloaltonetworks.com/CVE-2026-0263)
|
||||||
|
- [CVE-2026-0262](https://security.paloaltonetworks.com/CVE-2026-0262)
|
||||||
|
- [CVE-2026-0261](https://security.paloaltonetworks.com/CVE-2026-0261)
|
||||||
|
- [CVE-2026-0258](https://security.paloaltonetworks.com/CVE-2026-0258)
|
||||||
|
- [CVE-2026-0257](https://security.paloaltonetworks.com/CVE-2026-0257)
|
||||||
|
- [CVE-2026-0256](https://security.paloaltonetworks.com/CVE-2026-0256)
|
||||||
|
- [CVE-2026-0259](https://security.paloaltonetworks.com/CVE-2026-0259)
|
||||||
|
- [CVE-2026-0300](https://security.paloaltonetworks.com/CVE-2026-0300)
|
||||||
|
|
||||||
|
## PAN-323243
|
||||||
|
|
||||||
|
Fixed an issue where a configd crash occurred when the **Policies > Security** view was updated or refreshed in the web interface.
|
||||||
|
|
||||||
|
## PAN-317215
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls on ESXi with Intel E810 NICs using PCI passthrough
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the brdagent process became unresponsive during data port initialization, which resulted in system instability, interface outages, HA split-brain conditions, and unexpected reboots during failover.
|
||||||
|
|
||||||
|
## PAN-317155
|
||||||
|
|
||||||
|
Fixed an issue where the link status of log port 1 and log port 2 were unable to be monitored via SNMP due to the OIDs for the individual ports not being available.
|
||||||
|
|
||||||
|
## PAN-314875
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-7500 firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where firewall logs were not visible in the Strata Logging Service even though cloud logging was enabled and the firewall was successfully forwarding logs.
|
||||||
|
|
||||||
|
## PAN-314126
|
||||||
|
|
||||||
|
Fixed an issue where session rematch did not properly apply updated Security policy rules to existing traffic flows after committing changes, which caused traffic to still be allowed when a new Security policy was set to **Deny**.
|
||||||
|
|
||||||
|
## PAN-311166
|
||||||
|
|
||||||
|
Fixed an issue where the firewall rebooted unexpectedly to the all_task_1 process repeatedly restarting.
|
||||||
|
|
||||||
|
## PAN-310472
|
||||||
|
|
||||||
|
Fixed an issue on the web interface where checkboxes for **default information originate** and ABR in OSPF NSSA configurations were automatically enabled which resulted in unexpected configuration changes.
|
||||||
|
|
||||||
|
## PAN-308377
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-7050 firewalls in HA configurations only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the firewall reached 100% disk utilization due to the logrcvr process repeatedly restarting and dumping core files due to a blocked hints processing thread, which caused a failover.
|
||||||
|
|
||||||
|
## PAN-307714
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where insufficient i-node space was available on the sysroot0 partition.
|
||||||
|
|
||||||
|
## PAN-302196
|
||||||
|
|
||||||
|
Fixed an issue where the dataplane stopped responding when cleaning up expired sessions currently in Advanced Threat Prevention hold mode.
|
||||||
|
|
||||||
|
## PAN-277629
|
||||||
|
|
||||||
|
Fixed an issue where the firewall did not match the correct policy for SSL forward decrypted HTTP/2 traffic when upgrading from PAN-OS 10.2.9-h1 to PAN-OS 11.2.3.
|
||||||
@@ -0,0 +1,116 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 11.1.13-h5
|
||||||
|
---
|
||||||
|
|
||||||
|
## BLANK-000000
|
||||||
|
|
||||||
|
Fixes were made to address the following CVEs:
|
||||||
|
|
||||||
|
- [CVE-2026-0265](https://security.paloaltonetworks.com/CVE-2026-0265)
|
||||||
|
- [CVE-2026-0264](https://security.paloaltonetworks.com/CVE-2026-0264)
|
||||||
|
- [CVE-2026-0263](https://security.paloaltonetworks.com/CVE-2026-0263)
|
||||||
|
- [CVE-2026-0262](https://security.paloaltonetworks.com/CVE-2026-0262)
|
||||||
|
- [CVE-2026-0261](https://security.paloaltonetworks.com/CVE-2026-0261)
|
||||||
|
- [CVE-2026-0258](https://security.paloaltonetworks.com/CVE-2026-0258)
|
||||||
|
- [CVE-2026-0257](https://security.paloaltonetworks.com/CVE-2026-0257)
|
||||||
|
- [CVE-2026-0256](https://security.paloaltonetworks.com/CVE-2026-0256)
|
||||||
|
- [CVE-2026-0259](https://security.paloaltonetworks.com/CVE-2026-0259)
|
||||||
|
- [CVE-2026-0300](https://security.paloaltonetworks.com/CVE-2026-0300)
|
||||||
|
|
||||||
|
## PAN-323243
|
||||||
|
|
||||||
|
Fixed an issue where a configd crash occurred when the **Policies > Security** view was updated or refreshed in the web interface.
|
||||||
|
|
||||||
|
## PAN-318567
|
||||||
|
|
||||||
|
Fixed an issue where the OpenConfig plugin stopped working after a configuration update.
|
||||||
|
|
||||||
|
## PAN-317583
|
||||||
|
|
||||||
|
Fixed an issue with intermittent ICMP ping drops and packet loss in traffic flows between a hub and branch after upgrading to an affected PAN-OS release due to incorrect SD-WAN path monitor state.
|
||||||
|
|
||||||
|
## PAN-317466
|
||||||
|
|
||||||
|
Fixed an issue where SIP sessions stopped progressing after the firewall received fragmented packets, fragmented at header field.
|
||||||
|
|
||||||
|
## PAN-317215
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls on ESXi with Intel E810 NICs using PCI passthrough
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the brdagent process became unresponsive during data port initialization, which resulted in system instability, interface outages, HA split-brain conditions, and unexpected reboots during failover.
|
||||||
|
|
||||||
|
## PAN-317177
|
||||||
|
|
||||||
|
Fixed an issue on firewalls in DHCP Client mode where, after upgrading to an affected release, the SNMP process unexpectedly restarted after a commit, which led to false interface flap notifications on SNMP managers.
|
||||||
|
|
||||||
|
## PAN-317155
|
||||||
|
|
||||||
|
Fixed an issue where the link status of log port 1 and log port 2 were unable to be monitored via SNMP due to the OIDs for the individual ports not being available.
|
||||||
|
|
||||||
|
## PAN-316631
|
||||||
|
|
||||||
|
Fixed an issue BGP sessions experienced short disruptions across all peers, interfaces, and slots when a multicast event persisted longer than the NGP negotiated hold timers.
|
||||||
|
|
||||||
|
## PAN-314875
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-7500 firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where firewall logs were not visible in the Strata Logging Service even though cloud logging was enabled and the firewall was successfully forwarding logs.
|
||||||
|
|
||||||
|
## PAN-314435
|
||||||
|
|
||||||
|
Fixed an issue on the Panorama web interface where custom application tags for cloud applications were not consistently displayed in the Application Filter or application details even though the tags were configured via CLI and successfully enforced traffic blocking policy rules.
|
||||||
|
|
||||||
|
## PAN-314126
|
||||||
|
|
||||||
|
Fixed an issue where session rematch did not properly apply updated Security policy rules to existing traffic flows after committing changes, which caused traffic to still be allowed when a new Security policy was set to **Deny**.
|
||||||
|
|
||||||
|
## PAN-313193
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Firewalls in Layer 2 mode only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the new sessions were not able to be established due to the firewall intermittently dropping valid MAC address entries for specific VLANs when a manual switchover sent a high volume of traffic to the firewall.
|
||||||
|
|
||||||
|
## PAN-311248
|
||||||
|
|
||||||
|
Fixed an issue where the ABR failed to translate and advertise the default route (0.0.0.0/0) from an OSPF NSSA area into the OSPF backbone area as a Type-5 LSA.
|
||||||
|
|
||||||
|
## PAN-310472
|
||||||
|
|
||||||
|
Fixed an issue on the web interface where checkboxes for **default information originate** and ABR in OSPF NSSA configurations were automatically enabled which resulted in unexpected configuration changes.
|
||||||
|
|
||||||
|
## PAN-308377
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-7050 firewalls in HA configurations only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the firewall reached 100% disk utilization due to the logrcvr process repeatedly restarting and dumping core files due to a blocked hints processing thread, which caused a failover.
|
||||||
|
|
||||||
|
## PAN-307714
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where insufficient i-node space was available on the sysroot0 partition.
|
||||||
|
|
||||||
|
## PAN-295728
|
||||||
|
|
||||||
|
Fixed an issue where configuring an OSPFv2 NSSA area range caused OSPF-learned routes to become unreachable due to the incorrect installation of a discard route when the NSSA range prefix matched an existing OSPF route.
|
||||||
|
|
||||||
|
## PAN-295309
|
||||||
|
|
||||||
|
Fixed an issue where OSPF session using MD5 authentication experienced intermittent flapping due to out-of-order packet processing.
|
||||||
|
|
||||||
|
## PAN-277629
|
||||||
|
|
||||||
|
Fixed an issue where the firewall did not match the correct policy for SSL forward decrypted HTTP/2 traffic when upgrading from PAN-OS 10.2.9-h1 to PAN-OS 11.2.3.
|
||||||
@@ -0,0 +1,24 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 11.1.4-h33
|
||||||
|
---
|
||||||
|
|
||||||
|
## BLANK-000000
|
||||||
|
|
||||||
|
Fixes were made to address the following CVEs:
|
||||||
|
|
||||||
|
- [CVE-2026-0265](https://security.paloaltonetworks.com/CVE-2026-0265)
|
||||||
|
- [CVE-2026-0264](https://security.paloaltonetworks.com/CVE-2026-0264)
|
||||||
|
- [CVE-2026-0263](https://security.paloaltonetworks.com/CVE-2026-0263)
|
||||||
|
- [CVE-2026-0262](https://security.paloaltonetworks.com/CVE-2026-0262)
|
||||||
|
- [CVE-2026-0261](https://security.paloaltonetworks.com/CVE-2026-0261)
|
||||||
|
- [CVE-2026-0258](https://security.paloaltonetworks.com/CVE-2026-0258)
|
||||||
|
- [CVE-2026-0257](https://security.paloaltonetworks.com/CVE-2026-0257)
|
||||||
|
- [CVE-2026-0256](https://security.paloaltonetworks.com/CVE-2026-0256)
|
||||||
|
- [CVE-2026-0259](https://security.paloaltonetworks.com/CVE-2026-0259)
|
||||||
|
- [CVE-2026-0300](https://security.paloaltonetworks.com/CVE-2026-0300)
|
||||||
|
|
||||||
|
## PAN-265399
|
||||||
|
|
||||||
|
Fixed an issue where DNS queries for uppercase internal domain (SRV record) timed out when DNS Security was enabled.
|
||||||
@@ -0,0 +1,64 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 11.1.6-h32
|
||||||
|
---
|
||||||
|
|
||||||
|
## BLANK-000000
|
||||||
|
|
||||||
|
Fixes were made to address the following CVEs:
|
||||||
|
|
||||||
|
- [CVE-2026-0265](https://security.paloaltonetworks.com/CVE-2026-0265)
|
||||||
|
- [CVE-2026-0264](https://security.paloaltonetworks.com/CVE-2026-0264)
|
||||||
|
- [CVE-2026-0263](https://security.paloaltonetworks.com/CVE-2026-0263)
|
||||||
|
- [CVE-2026-0262](https://security.paloaltonetworks.com/CVE-2026-0262)
|
||||||
|
- [CVE-2026-0261](https://security.paloaltonetworks.com/CVE-2026-0261)
|
||||||
|
- [CVE-2026-0258](https://security.paloaltonetworks.com/CVE-2026-0258)
|
||||||
|
- [CVE-2026-0257](https://security.paloaltonetworks.com/CVE-2026-0257)
|
||||||
|
- [CVE-2026-0256](https://security.paloaltonetworks.com/CVE-2026-0256)
|
||||||
|
- [CVE-2026-0259](https://security.paloaltonetworks.com/CVE-2026-0259)
|
||||||
|
- [CVE-2026-0300](https://security.paloaltonetworks.com/CVE-2026-0300)
|
||||||
|
|
||||||
|
## PAN-323243
|
||||||
|
|
||||||
|
Fixed an issue where a configd crash occurred when the **Policies > Security** view was updated or refreshed in the web interface.
|
||||||
|
|
||||||
|
## PAN-322281
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
Firewalls in HA configurations only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the HA 2 interface did not come up on the passive firewall, which resulted in the firewall being unable to join the HA pair.
|
||||||
|
|
||||||
|
## PAN-314126
|
||||||
|
|
||||||
|
Fixed an issue where session rematch did not properly apply updated Security policy rules to existing traffic flows after committing changes, which caused traffic to still be allowed when a new Security policy was set to **Deny**.
|
||||||
|
|
||||||
|
## PAN-311166
|
||||||
|
|
||||||
|
Fixed an issue where the firewall rebooted unexpectedly to the all_task_1 process repeatedly restarting.
|
||||||
|
|
||||||
|
## PAN-308377
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-7050 firewalls in HA configurations only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the firewall reached 100% disk utilization due to the logrcvr process repeatedly restarting and dumping core files due to a blocked hints processing thread, which caused a failover.
|
||||||
|
|
||||||
|
## PAN-307901
|
||||||
|
|
||||||
|
Fixed an issue where a leak in decryption counters caused resource exhaustion, which led to a GlobalProtect service outage.
|
||||||
|
|
||||||
|
## PAN-307714
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where insufficient i-node space was available on the sysroot0 partition.
|
||||||
|
|
||||||
|
## PAN-302196
|
||||||
|
|
||||||
|
Fixed an issue where the dataplane stopped responding when cleaning up expired sessions currently in Advanced Threat Prevention hold mode.
|
||||||
@@ -0,0 +1,9 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 11.1.7-h6
|
||||||
|
---
|
||||||
|
|
||||||
|
## BLANK-000000
|
||||||
|
|
||||||
|
This hotfix includes performance and bug fixes.
|
||||||
@@ -0,0 +1,63 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 11.2.10-h6
|
||||||
|
---
|
||||||
|
|
||||||
|
## BLANK-000000
|
||||||
|
|
||||||
|
Fixes were made to address the following CVEs:
|
||||||
|
|
||||||
|
- [CVE-2026-0265](https://security.paloaltonetworks.com/CVE-2026-0265)
|
||||||
|
- [CVE-2026-0264](https://security.paloaltonetworks.com/CVE-2026-0264)
|
||||||
|
- [CVE-2026-0263](https://security.paloaltonetworks.com/CVE-2026-0263)
|
||||||
|
- [CVE-2026-0262](https://security.paloaltonetworks.com/CVE-2026-0262)
|
||||||
|
- [CVE-2026-0261](https://security.paloaltonetworks.com/CVE-2026-0261)
|
||||||
|
- [CVE-2026-0258](https://security.paloaltonetworks.com/CVE-2026-0258)
|
||||||
|
- [CVE-2026-0256](https://security.paloaltonetworks.com/CVE-2026-0256)
|
||||||
|
- [CVE-2026-0259](https://security.paloaltonetworks.com/CVE-2026-0259)
|
||||||
|
- [CVE-2026-0300](https://security.paloaltonetworks.com/CVE-2026-0300)
|
||||||
|
|
||||||
|
## PAN-317215
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
VM-Series firewalls on ESXi with Intel E810 NICs using PCI passthrough
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the brdagent process became unresponsive during data port initialization, which resulted in system instability, interface outages, HA split-brain conditions, and unexpected reboots during failover.
|
||||||
|
|
||||||
|
## PAN-315919
|
||||||
|
|
||||||
|
Fixed an issue where GlobalProtect pre-logon tunnel session was not cleared even after the user was logged in. With this fix, the session is cleared after the session timeout expires.
|
||||||
|
|
||||||
|
## PAN-313849
|
||||||
|
|
||||||
|
Fixed an issue on Panorama where the logd process exited unexpectedly when handling syslog forwarding.
|
||||||
|
|
||||||
|
## PAN-311192
|
||||||
|
|
||||||
|
Fixed an issue where the device-telemetry collect-now process became unresponsive when the process was initiated multiple times with other processes running concurrently, which prevented subsequent telemetry collection.
|
||||||
|
|
||||||
|
## PAN-308377
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-7050 firewalls in HA configurations only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the firewall reached 100% disk utilization due to the logrcvr process repeatedly restarting and dumping core files due to a blocked hints processing thread, which caused a failover.
|
||||||
|
|
||||||
|
## PAN-306356
|
||||||
|
|
||||||
|
Fixed an issue where the logrcvr process on a firewall stopped responding due to a document node being unexpectedly freed.
|
||||||
|
|
||||||
|
## PAN-303663
|
||||||
|
|
||||||
|
Fixed an issue on the firewall where SolarWinds monitoring systems reported 100% usage for Slot1 Data Processor-0 Hardware Packet Buffers due to an inaccurate reported packet buffer.
|
||||||
|
|
||||||
|
## PAN-295806
|
||||||
|
|
||||||
|
Fixed an issue where memory leaks on the configd process occurred due to a hash insert operation failing during connection management and SSL connections.
|
||||||
|
|
||||||
|
## PAN-288175
|
||||||
|
|
||||||
|
Addressed a stack buffer overflow memory leak under plugin management code path.
|
||||||
@@ -0,0 +1,377 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 11.2.10-h7
|
||||||
|
---
|
||||||
|
|
||||||
|
## PAN-314201
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 12.1.6 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
On firewalls running PAN-OS 12.1, IPsec VPN tunnels to third-party peer devices may experience intermittent traffic loss during rekey operations. When a new Security Association (SA) forms before the old SA expires, traffic may stop flowing until the older SA naturally expires or you manually clear it. During this time, the output of show vpn ipsec-sa may show two SAs for the same proxy ID. This issue primarily affects tunnels to third-party peer devices and does not occur with Palo Alto Networks to Palo Alto Networks tunnels.
|
||||||
|
|
||||||
|
**Workaround:** Manually clear the affected Security Association using the command clear vpn ipsec-sa tunnel <tunnel-name> to restore connectivity.
|
||||||
|
|
||||||
|
## PAN-313623
|
||||||
|
|
||||||
|
On firewalls with TPM (Trusted Platform Module) support, device certificate renewals may fail due to a disk partition being full. This latter occurs because temporary files aren't being deleted during device certificate status checks.
|
||||||
|
|
||||||
|
## PAN-312706
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 12.1.5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Firewalls may restart unexpectedly due to an internal error in content inspection processing. This issue can occur when the firewall is performing antivirus scanning, URL filtering, or WildFire analysis.
|
||||||
|
|
||||||
|
## PAN-309604
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5500 series only
|
||||||
|
```
|
||||||
|
|
||||||
|
In some rare cases, the front panel PSU status LED might show amber, even when the LEDs on the PSU show green.
|
||||||
|
|
||||||
|
## PAN-309602
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5500 series only
|
||||||
|
```
|
||||||
|
|
||||||
|
When the firewall is initially powered on, the FAN-0 LED does not turn on. The fan functions correctly, but the LED doesn't reflect the status.
|
||||||
|
|
||||||
|
**Workaround:** Remove and reinsert the fan to turn on the LED.
|
||||||
|
|
||||||
|
## PAN-308564
|
||||||
|
|
||||||
|
Packets are dropped on SD-WAN interfaces if they require fragmentation for an interface but have the **Don't Fragment (DF)** bit set. This results in unexpected packet drops. This affects client to server sessions when using SD-WAN for NGFW.
|
||||||
|
|
||||||
|
**Workaround:** Allow fragmenting packets with DF bit set (debug dataplane set ip4-ignore-df yes).
|
||||||
|
|
||||||
|
## PAN-308507
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 12.1.6 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Strata Logging Service (SLS) log-forwarding streams intermittently show as inactive. When checking the status of log-forwarding connections, one or more streams are reported as inactive. Restarting the log-receiver process temporarily resolves the issue, but the streams become inactive again after approximately 1-2 hours. This intermittent inactivity results in log loss.
|
||||||
|
|
||||||
|
## PAN-307702
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 12.1.5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
When LACP pre-negotiation is enabled on firewalls in HA configurations, traffic passing through aggregate Ethernet (AE) interfaces may be interrupted for several minutes during HA failovers. This occurs because the suspended (formerly active) firewall continues to forward packets for active sessions even after the failover completes, causing MAC address flapping on neighboring switches.
|
||||||
|
|
||||||
|
## PAN-305880
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-7500 firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
Intermittent internet connectivity failures on the logging interface might trigger a dataplane disconnect from Strata Logging Service (SLS) and WildFire cloud.
|
||||||
|
|
||||||
|
## PAN-305301
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 12.1.5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
The timing of GlobalProtect lifetime expiry or inactivity logout notifications used for GlobalProtect SSL tunnels may cause the pan_task process to stop responding and the dataplane to restart.
|
||||||
|
|
||||||
|
**Workaround:** Select **Network > GlobalProtect > Gateways > <gateway-config> > Agent > <agent-config> > Connection Settings** and change the value of both **Notify Before Lifetime Expires (min)** and **Notify Before Inactivity Logout (min)** to 0.
|
||||||
|
|
||||||
|
## PAN-304718
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 12.1.5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
When using GlobalProtect Clientless VPN, the firewall may restart unexpectedly, causing routing protocol (OSPF and BGP) outages. This issue occurs during web content processing for clientless VPN sessions.
|
||||||
|
|
||||||
|
**Workaround:** To prevent this issue until you can upgrade to a fixed release, disable clientless VPN in your GlobalProtect portal configuration.
|
||||||
|
|
||||||
|
## PAN-304576
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 12.1.5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Traffic interruption may occur when inspection of HTTP/2 traffic is enabled.
|
||||||
|
|
||||||
|
**Workaround:** Disable HTTP/2 server push using the set deviceconfig setting http2 server-push no CLI command.
|
||||||
|
|
||||||
|
## PAN-303959
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 12.1.5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Traffic that is incorrectly identified as unknown-tcp/unknown-udp eventually drops due to an App-ID resource limitation issue.
|
||||||
|
|
||||||
|
## PAN-303663
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 12.1.5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
After upgrading to an affected release, SNMP monitoring systems such as SolarWinds may report 100% usage for hardware packet buffers on PA-3400 Series and PA-5450 firewalls, even when the firewall is idle and packet buffer utilization is normal. The packet buffer utilization oid is fixed to not show incorrect values.
|
||||||
|
|
||||||
|
## PAN-300850
|
||||||
|
|
||||||
|
Manual scheduling of cloud verdicts is required if a new host in an Host Compliance Service-enabled environment has a refresh event entry without a corresponding update event entry.
|
||||||
|
|
||||||
|
## PAN-300809
|
||||||
|
|
||||||
|
Host Compliance Service connectivity will not work if it is connected with management IP which is configured with DHCP mode.
|
||||||
|
|
||||||
|
## PAN-300677
|
||||||
|
|
||||||
|
Panorama cannot display Threat log entries (**Monitor > Logs > Threat**) when the managed log collector is running a lower PAN-OS release than Panorama.
|
||||||
|
|
||||||
|
Workaround: Upgrade the log collectors to the same version as Panorama.
|
||||||
|
|
||||||
|
## PAN-300671
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 12.1.5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
Traffic reports that display destination/source IP addresses or destination/source hostnames may incorrectly show IPv4 addresses in IPv6 format (for example, ::ffff:x.x.x.x). This issue affects both custom reports and scheduled reports, including PDF exports.
|
||||||
|
|
||||||
|
## PAN-300627
|
||||||
|
|
||||||
|
AutoCommit fails when the Traffic Object is used on AI Runtime Security, which consequently impacts the workloads that utilize overlapping subnets.
|
||||||
|
|
||||||
|
## PAN-300483
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-7500 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Enabling FIPS-CC mode causes the firewall to go into maintenance mode.
|
||||||
|
|
||||||
|
**Workaround**: After the firewall goes into maintenance mode, perform an additional reboot. The firewall will successfully start up in FIPS-CC mode.
|
||||||
|
|
||||||
|
## PAN-300467
|
||||||
|
|
||||||
|
WildFire WF-500 appliances running PAN-OS 10.x or PAN-OS 11.x cannot be managed by Panorama running PAN-OS 12.1.2 due to connectivity issues.
|
||||||
|
|
||||||
|
**Workaround:** Upgrade your WildFire appliances to PAN-OS 12.1.2 or later.
|
||||||
|
|
||||||
|
## PAN-300407
|
||||||
|
|
||||||
|
The Release Note URL column in the Panorama > Plugins page is empty.
|
||||||
|
|
||||||
|
Release Notes for the plugins are available in the [plugins release notes](https://docs.paloaltonetworks.com/plugins/vm-series-and-panorama-plugins-release-notes) or in their individual product release notes.
|
||||||
|
|
||||||
|
## PAN-300230
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
NGFW Cluster
|
||||||
|
```
|
||||||
|
|
||||||
|
In an NGFW cluster, your pings to the HSCI-B link might fail, even when the link indicates it is up. In the event that the HSCI-A link is brought down or unplugged, the cluster node will transition to failed state, avoiding split brain as both HSCI links are down in this case.
|
||||||
|
|
||||||
|
**Workaround**: Reboot the cluster node to resolve the HSCI-B ping issue.
|
||||||
|
|
||||||
|
## PAN-300192
|
||||||
|
|
||||||
|
If the Host Compliance Service is configured with a service route pointing to an unreachable IP address, the gp_broker process may stop working when you enable-disable the Host Compliance Service.
|
||||||
|
|
||||||
|
## PAN-300114
|
||||||
|
|
||||||
|
VM entered maintenance mode during a downgrade from version 12.1.2 to 11.2.7, when executed through the CLI.
|
||||||
|
|
||||||
|
**Workaround**: Download and install the required version of PAN-OS through the UI instead of the CLI.
|
||||||
|
|
||||||
|
## PAN-300069
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-410 firewall only
|
||||||
|
```
|
||||||
|
|
||||||
|
Loading a saved config file can take up to 5 minutes.
|
||||||
|
|
||||||
|
## PAN-300053
|
||||||
|
|
||||||
|
When you use the CLI command request system fqdn refresh to trigger another IP address resolution of configured FQDN entries, the firewall might get into an error state where the DNS Proxy cache received and stored a new IP address for a particular FQDN entry via this command. However, the Device-Server (and the Security rule) still have the old IP address for that FQDN entry.
|
||||||
|
|
||||||
|
**Workaround**: Avoid using the CLI command: request system fqdn refresh. Use the following command instead (for a particular domain-name or an entire list): clear dns-proxy cache all domain-name <domain_name>. To correct the error state where the DNS Proxy cache and Device-Server and Security rule are already storing different IP addresses, use the following CLI command: debug device-server dump fqdn type resync vsys <vsys_name> fqdn-name <domain_name>
|
||||||
|
|
||||||
|
## PAN-300025
|
||||||
|
|
||||||
|
If Azure hotplug events occur, the firewall may experience a brdagent crash and data interfaces may transition to an unknown state, leading to traffic disruption.
|
||||||
|
|
||||||
|
**Workaround**: Reboot the VM if the brdagent crash does not trigger a device reboot.
|
||||||
|
|
||||||
|
## PAN-299562
|
||||||
|
|
||||||
|
SSL proxy sessions fail when clients send a Client Hello with TLSv1.2 and TLSv1.3, and exclusively prefer the secp192 elliptic curve.
|
||||||
|
|
||||||
|
**Workaround**: To address this, configure a decryption profile to use TLSv1.2 as the maximum supported TLS version. Then, apply this profile to the decryption policy rules for the affected clients and servers. This enables the client to modify its preferred curves, facilitating successful session establishment.
|
||||||
|
|
||||||
|
## PAN-299387
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
NGFW Cluster
|
||||||
|
```
|
||||||
|
|
||||||
|
When an NGFW cluster has only one firewall node present and powered up, that node is stuck in UNKNOWN state after you reboot it and it comes back up. The issue occurs in two scenarios:
|
||||||
|
|
||||||
|
- When there is only one node configured in the cluster (no peer is available or configured).
|
||||||
|
- When the peer device in the cluster is completely powered down or unable to autonegotiate its connected HSCI ports. That is, two nodes are in the cluster, but only one node is booting up while the other remains down completely.
|
||||||
|
|
||||||
|
The expected behavior is that if no peer device is available (at a port autonegotiation or link level for HSCI-A or HSCI-B), then a cluster device should go to INITIAL state, followed by ONLINE state (and not remain in UNKNOWN state).
|
||||||
|
|
||||||
|
**Workaround**: To avoid this issue, connect the HSCI-A to HSCI-B in loopback to create a link partner.
|
||||||
|
|
||||||
|
## PAN-299229
|
||||||
|
|
||||||
|
On PA-5400 Series and PA-7500 Series firewalls, if you run certain types of CLI commands during or shortly after a commit, the commands will time out. The types of CLI commands impacted by this issue are IoT, Cloud-User-ID, and App-ID Cloud Engine CLI commands.
|
||||||
|
|
||||||
|
**Workaround**: Don't execute IoT, Cloud-User-ID, or App-ID Cloud Engine CLI commands during or shortly after a commit on a PA-5400 Series or PA-7500 Series firewall.
|
||||||
|
|
||||||
|
## PAN-299170
|
||||||
|
|
||||||
|
The remediation link included in the generated PDF of an upgrade check report might be pruned due to a text length limitation of the export function. The link remains fully functional and works correctly on the Panorama web interface.
|
||||||
|
|
||||||
|
## PAN-299114
|
||||||
|
|
||||||
|
After you enable the **Enable Duplicate Logging (Cloud and On-Premise)**setting on a firewall, clicking **Status for Cloud Logging**, does not display the logging service connection status.
|
||||||
|
|
||||||
|
## PAN-298540
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-5500 Series firewalls only
|
||||||
|
```
|
||||||
|
|
||||||
|
The **Monitor** tab in the Web Interface does not display a pop-up to indicate that high-speed log forwarding is enabled and that logs are only viewable from Panorama.
|
||||||
|
|
||||||
|
## PAN-298083
|
||||||
|
|
||||||
|
After you change the system mode on an M-700 appliance from Panorama mode to PAN-DB private cloud mode, the snmpd process fails to work.
|
||||||
|
|
||||||
|
## PAN-298047
|
||||||
|
|
||||||
|
In an AI Runtime Security environment, the Azure Container outbound traffic does not seem to be functional and the egress traffic is being misdirected to an incorrect cluster node port.
|
||||||
|
|
||||||
|
## PAN-297772
|
||||||
|
|
||||||
|
When an Intel e810 NIC is configured in SR-IOV mode, sharing Virtual Functions (VFs) among multiple HSF cluster nodes and subsequently rebooting a cluster node while traffic is active may result in traffic disruption on other HSF cluster nodes utilizing the same NIC. It is recommended to refrain from sharing Intel e810 VFs across cluster nodes and to allocate one VF per Intel e810 PF.
|
||||||
|
|
||||||
|
## PAN-297610
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 12.1.5 Addressed Issues.
|
||||||
|
```
|
||||||
|
|
||||||
|
A firewall may become unresponsive after an upgrade due to the `fsck` command scanning drive partitions in parallel with the root partition, causing the process to take an extended amount of time.
|
||||||
|
|
||||||
|
## PAN-297114
|
||||||
|
|
||||||
|
After successfully generating a health check report for managed firewalls from Panorama, the progress bar does not appear and the latest health check reports are not displayed (**Panorama > Device Deployment > Upgrade Check**).
|
||||||
|
|
||||||
|
**Workaround**: Manually refresh the page to see the latest reports.
|
||||||
|
|
||||||
|
## PAN-295803
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
This issue is now resolved. See PAN-OS 12.1.5 Addressed Issues
|
||||||
|
```
|
||||||
|
|
||||||
|
A configd memory leak occurs post commit (during Panorama connectivity check), potentially leading to OOM (out of memory condition) and device reboot.
|
||||||
|
|
||||||
|
## PAN-294687
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
NGFW Clusters
|
||||||
|
```
|
||||||
|
|
||||||
|
In an NGFW cluster, the leader can't retrieve the HIP Report from Panorama, nor synchronize it to the non-leader nodes. Unlike HA Active/Passive mode, both leader and non-leader nodes receive traffic in cluster mode. If the relevant HIP Report is missing, policies involving HIP may not work properly. The expected behavior is that when a non-leader node receives related traffic, it should request the corresponding HIP Report from the leader.
|
||||||
|
|
||||||
|
## PAN-293754
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
NGFW Clusters
|
||||||
|
```
|
||||||
|
|
||||||
|
Firewalls in an NGFW cluster indicate they are in ONLINE state even though their configurations are different (they aren't synchronized).
|
||||||
|
|
||||||
|
**Workaround**: Push the configuration from Panorama to all cluster members at the same time; don't push to an individual firewall. If a cluster member isn't connected to Panorama during the push, the push will fail to the disconnected firewall, but will succeed to all connected firewalls.
|
||||||
|
|
||||||
|
## PAN-293718
|
||||||
|
|
||||||
|
When high speed logging is enabled on a PA-5560 device, the expected warning message is not displayed on the web interface. This prevents administrators from being notified that logs can only be viewed from Panorama.
|
||||||
|
|
||||||
|
## PAN-292601
|
||||||
|
|
||||||
|
PAN-OS 12.1.2 and later 12.1 releases support a Load Balanced DNS configuration for an address object. If there are two address objects with same FQDN, but one object has Load Balanced DNS enabled and other object has Load Balanced DNS disabled, then the policy match for the removed IP addresses doesn't work as expected.
|
||||||
|
|
||||||
|
**Workaround**: Enable (or disable) Load Balanced DNS consistently for an FQDN that is used with multiple address objects.
|
||||||
|
|
||||||
|
## PAN-290692
|
||||||
|
|
||||||
|
In Host Compliance Service, when you create a 'Shared' type Host Compliance Object for the 'Disk-Encryption' category, the State drop-down is automatically selected and cannot be edited. However, you can change the state later by editing the object, if required.
|
||||||
|
|
||||||
|
## PAN-289524
|
||||||
|
|
||||||
|
In PAN-OS 12.1.2 and later 12.1 releases, PAN-OS can obtain resolved IP addresses from a Load balanced DNS server and use them in a policy match. However, this functionality does not work as intended when the DNS cache reuse flag is enabled. When the DNS cache reuse flag is enabled, the DNS resolution works as if the Load balanced DNS flag (for an Address object) is disabled.
|
||||||
|
|
||||||
|
## PAN-286496
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
NGFW Clusters
|
||||||
|
```
|
||||||
|
|
||||||
|
URL-continue and override continue selections will function like a general URL-block action.
|
||||||
|
|
||||||
|
## PAN-283429
|
||||||
|
|
||||||
|
When you use custom certificates for the connection between Panorama and a log collector, the automated renewal for the predefined ElasticSearch certificates gets disrupted.
|
||||||
|
|
||||||
|
**Workaround**: Remove the custom certificates before the ElasticSearch certificates expire. This allows the system to correctly identify and renew the predefined ElasticSearch certificates. After the renewal is complete, re-install the custom certificates.
|
||||||
|
|
||||||
|
## PAN-283053
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-7000 Series with Log Forwarding Card only
|
||||||
|
```
|
||||||
|
|
||||||
|
When the firewall is configured to forward logs to an external log collector or Strata Logging Service, the firewall root partition may reach high disk utilization, which can cause the firewall to become non-functional. This occurs when the log collector is temporarily unavailable or unable to process logs at the rate the firewall is sending them.
|
||||||
|
|
||||||
|
**Workaround:** To help prevent this issue, ensure network connectivity between the firewall and log collector is stable and verify that the log collector has sufficient capacity to handle the volume of logs generated by your deployment.
|
||||||
|
|
||||||
|
## PAN-237106
|
||||||
|
|
||||||
|
LSVPN satellite certificates may be generated with serial numbers exceeding 40 hexadecimal characters. This causes certificate revocation and deletion operations to fail with the following error messages:
|
||||||
|
|
||||||
|
- db-serialno can be at most 40 characters
|
||||||
|
- db-serialno is invalid
|
||||||
|
|
||||||
|
**Workaround:**
|
||||||
|
|
||||||
|
To resolve this issue, use the following CLI commands with the LSVPN satellite serial number to manually delete or revoke the affected certificates:
|
||||||
|
|
||||||
|
**Delete certificate information**:delete sslmgr-store certificate-info portal name <name> serialno <satellite_serial>
|
||||||
|
|
||||||
|
**Revoke satellite certificates**:delete sslmgr-store satellite-info-revoke-certificate portal <name> serialno <list_of_satellite_serials>
|
||||||
|
|
||||||
|
## PLUG-21065
|
||||||
|
|
||||||
|
In a PA-VM or AI Runtime Security environment, it is observed that the Software Firewall Orchestration plugin deployed with a VM-Flex license and configured with 8-14 GB of memory may encounter traffic disruptions when jumbo frames are enabled. It is recommended to disable jumbo frames on these lower-end VMs in version 12.1.2 by executing the command: set system setting jumbo-frame off.
|
||||||
|
|
||||||
|
## PLUG-19238
|
||||||
|
|
||||||
|
Enabling Advanced Routing through bootstrap on VM-Series and Prisma AIRS is not supported.
|
||||||
|
|
||||||
|
**Workaround**: After the firewall boots up, enable advanced routing using the CLI command set device-management general-settings advance-routing yes or enable [advanced routing](https://docs.paloaltonetworks.com/pan-os/11-1/pan-os-networking-admin/advanced-routing/enable-advanced-routing) through the UI.
|
||||||
|
|
||||||
|
## DRS-6556
|
||||||
|
|
||||||
|
For Host Compliance Service, while configuring Mappings & Tags in CIE and when you click on the **HIP Report** tab, the following error message is displayed even when the response is successful:
|
||||||
|
|
||||||
|
**getaddrinfo ENOTFOUND null**
|
||||||
@@ -0,0 +1,63 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 11.2.7-h13
|
||||||
|
---
|
||||||
|
|
||||||
|
## BLANK-000000
|
||||||
|
|
||||||
|
Fixes were made to address the following CVEs:
|
||||||
|
|
||||||
|
- [CVE-2026-0265](https://security.paloaltonetworks.com/CVE-2026-0265)
|
||||||
|
- [CVE-2026-0264](https://security.paloaltonetworks.com/CVE-2026-0264)
|
||||||
|
- [CVE-2026-0263](https://security.paloaltonetworks.com/CVE-2026-0263)
|
||||||
|
- [CVE-2026-0262](https://security.paloaltonetworks.com/CVE-2026-0262)
|
||||||
|
- [CVE-2026-0261](https://security.paloaltonetworks.com/CVE-2026-0261)
|
||||||
|
- [CVE-2026-0258](https://security.paloaltonetworks.com/CVE-2026-0258)
|
||||||
|
- [CVE-2026-0256](https://security.paloaltonetworks.com/CVE-2026-0256)
|
||||||
|
- [CVE-2026-0259](https://security.paloaltonetworks.com/CVE-2026-0259)
|
||||||
|
- [CVE-2026-0300](https://security.paloaltonetworks.com/CVE-2026-0300)
|
||||||
|
|
||||||
|
## PAN-317772
|
||||||
|
|
||||||
|
Added a fix to improve performance in lossy network conditions.
|
||||||
|
|
||||||
|
## PAN-315965
|
||||||
|
|
||||||
|
Fixed an issue to address TCP proxy fast recovery behavior to follow RFC 5681.
|
||||||
|
|
||||||
|
## PAN-315919
|
||||||
|
|
||||||
|
Fixed an issue where GlobalProtect pre-logon tunnel session was not cleared even after the user was logged in. With this fix, the session is cleared after the session timeout expires.
|
||||||
|
|
||||||
|
## PAN-311192
|
||||||
|
|
||||||
|
Fixed an issue where the device-telemetry collect-now process became unresponsive when the process was initiated multiple times with other processes running concurrently, which prevented subsequent telemetry collection.
|
||||||
|
|
||||||
|
## PAN-308377
|
||||||
|
|
||||||
|
```caveat
|
||||||
|
PA-7050 firewalls in HA configurations only
|
||||||
|
```
|
||||||
|
|
||||||
|
Fixed an issue where the firewall reached 100% disk utilization due to the logrcvr process repeatedly restarting and dumping core files due to a blocked hints processing thread, which caused a failover.
|
||||||
|
|
||||||
|
## PAN-306356
|
||||||
|
|
||||||
|
Fixed an issue where the logrcvr process on a firewall stopped responding due to a document node being unexpectedly freed.
|
||||||
|
|
||||||
|
## PAN-303663
|
||||||
|
|
||||||
|
Fixed an issue on the firewall where SolarWinds monitoring systems reported 100% usage for Slot1 Data Processor-0 Hardware Packet Buffers due to an inaccurate reported packet buffer.
|
||||||
|
|
||||||
|
## PAN-295806
|
||||||
|
|
||||||
|
Fixed an issue where memory leaks on the configd process occurred due to a hash insert operation failing during connection management and SSL connections.
|
||||||
|
|
||||||
|
## PAN-288175
|
||||||
|
|
||||||
|
Addressed a stack buffer overflow memory leak under plugin management code path.
|
||||||
|
|
||||||
|
## PAN-251024
|
||||||
|
|
||||||
|
Fixed an issue where GlobalProtect logs did not show the correct region for the IP address due to content updates not retrieving the latest configuration.
|
||||||
@@ -0,0 +1,9 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 11.2.7-h14
|
||||||
|
---
|
||||||
|
|
||||||
|
## BLANK-000000
|
||||||
|
|
||||||
|
A fix was made to address [CVE-2026-0257](https://security.paloaltonetworks.com/CVE-2026-0257).
|
||||||
@@ -0,0 +1,19 @@
|
|||||||
|
---
|
||||||
|
type: Addressed
|
||||||
|
product: PAN-OS
|
||||||
|
version: 12.1.4-h5
|
||||||
|
---
|
||||||
|
|
||||||
|
## BLANK-000000
|
||||||
|
|
||||||
|
Fixes were made to address the following CVEs:
|
||||||
|
|
||||||
|
- [CVE-2026-0265](https://security.paloaltonetworks.com/CVE-2026-0265)
|
||||||
|
- [CVE-2026-0264](https://security.paloaltonetworks.com/CVE-2026-0264)
|
||||||
|
- [CVE-2026-0263](https://security.paloaltonetworks.com/CVE-2026-0263)
|
||||||
|
- [CVE-2026-0262](https://security.paloaltonetworks.com/CVE-2026-0262)
|
||||||
|
- [CVE-2026-0261](https://security.paloaltonetworks.com/CVE-2026-0261)
|
||||||
|
- [CVE-2026-0258](https://security.paloaltonetworks.com/CVE-2026-0258)
|
||||||
|
- [CVE-2026-0257](https://security.paloaltonetworks.com/CVE-2026-0257)
|
||||||
|
- [CVE-2026-0256](https://security.paloaltonetworks.com/CVE-2026-0256)
|
||||||
|
- [CVE-2026-0259](https://security.paloaltonetworks.com/CVE-2026-0259)
|
||||||
+15
-1
@@ -10,6 +10,7 @@
|
|||||||
"12.1.4.md",
|
"12.1.4.md",
|
||||||
"12.1.4-h2.md",
|
"12.1.4-h2.md",
|
||||||
"12.1.4-h3.md",
|
"12.1.4-h3.md",
|
||||||
|
"12.1.4-h5.md",
|
||||||
"12.1.5.md",
|
"12.1.5.md",
|
||||||
"12.1.6.md"
|
"12.1.6.md"
|
||||||
],
|
],
|
||||||
@@ -62,6 +63,8 @@
|
|||||||
"11.2.7-h10.md",
|
"11.2.7-h10.md",
|
||||||
"11.2.7-h11.md",
|
"11.2.7-h11.md",
|
||||||
"11.2.7-h12.md",
|
"11.2.7-h12.md",
|
||||||
|
"11.2.7-h13.md",
|
||||||
|
"11.2.7-h14.md",
|
||||||
"11.2.8.md",
|
"11.2.8.md",
|
||||||
"11.2.9.md",
|
"11.2.9.md",
|
||||||
"11.2.10.md",
|
"11.2.10.md",
|
||||||
@@ -70,6 +73,8 @@
|
|||||||
"11.2.10-h3.md",
|
"11.2.10-h3.md",
|
||||||
"11.2.10-h4.md",
|
"11.2.10-h4.md",
|
||||||
"11.2.10-h5.md",
|
"11.2.10-h5.md",
|
||||||
|
"11.2.10-h6.md",
|
||||||
|
"11.2.10-h7.md",
|
||||||
"11.2.11.md"
|
"11.2.11.md"
|
||||||
],
|
],
|
||||||
"known": [
|
"known": [
|
||||||
@@ -128,6 +133,7 @@
|
|||||||
"11.1.4-h25.md",
|
"11.1.4-h25.md",
|
||||||
"11.1.4-h27.md",
|
"11.1.4-h27.md",
|
||||||
"11.1.4-h32.md",
|
"11.1.4-h32.md",
|
||||||
|
"11.1.4-h33.md",
|
||||||
"11.1.5.md",
|
"11.1.5.md",
|
||||||
"11.1.5-h1.md",
|
"11.1.5-h1.md",
|
||||||
"11.1.6.md",
|
"11.1.6.md",
|
||||||
@@ -147,10 +153,12 @@
|
|||||||
"11.1.6-h23.md",
|
"11.1.6-h23.md",
|
||||||
"11.1.6-h25.md",
|
"11.1.6-h25.md",
|
||||||
"11.1.6-h29.md",
|
"11.1.6-h29.md",
|
||||||
|
"11.1.6-h32.md",
|
||||||
"11.1.7.md",
|
"11.1.7.md",
|
||||||
"11.1.7-h1.md",
|
"11.1.7-h1.md",
|
||||||
"11.1.7-h2.md",
|
"11.1.7-h2.md",
|
||||||
"11.1.7-h4.md",
|
"11.1.7-h4.md",
|
||||||
|
"11.1.7-h6.md",
|
||||||
"11.1.8.md",
|
"11.1.8.md",
|
||||||
"11.1.9.md",
|
"11.1.9.md",
|
||||||
"11.1.10.md",
|
"11.1.10.md",
|
||||||
@@ -162,12 +170,14 @@
|
|||||||
"11.1.10-h10.md",
|
"11.1.10-h10.md",
|
||||||
"11.1.10-h12.md",
|
"11.1.10-h12.md",
|
||||||
"11.1.10-h21.md",
|
"11.1.10-h21.md",
|
||||||
|
"11.1.10-h25.md",
|
||||||
"11.1.11.md",
|
"11.1.11.md",
|
||||||
"11.1.12.md",
|
"11.1.12.md",
|
||||||
"11.1.13.md",
|
"11.1.13.md",
|
||||||
"11.1.13-h1.md",
|
"11.1.13-h1.md",
|
||||||
"11.1.13-h2.md",
|
"11.1.13-h2.md",
|
||||||
"11.1.13-h3.md",
|
"11.1.13-h3.md",
|
||||||
|
"11.1.13-h5.md",
|
||||||
"11.1.14.md"
|
"11.1.14.md"
|
||||||
],
|
],
|
||||||
"known": [
|
"known": [
|
||||||
@@ -292,6 +302,9 @@
|
|||||||
"10.2.10-h17.md",
|
"10.2.10-h17.md",
|
||||||
"10.2.10-h18.md",
|
"10.2.10-h18.md",
|
||||||
"10.2.10-h21.md",
|
"10.2.10-h21.md",
|
||||||
|
"10.2.10-h30.md",
|
||||||
|
"10.2.10-h31.md",
|
||||||
|
"10.2.10-h36.md",
|
||||||
"10.2.11.md",
|
"10.2.11.md",
|
||||||
"10.2.11-h1.md",
|
"10.2.11-h1.md",
|
||||||
"10.2.11-h6.md",
|
"10.2.11-h6.md",
|
||||||
@@ -309,7 +322,8 @@
|
|||||||
"10.2.16.md",
|
"10.2.16.md",
|
||||||
"10.2.18.md",
|
"10.2.18.md",
|
||||||
"10.2.18-h1.md",
|
"10.2.18-h1.md",
|
||||||
"10.2.18-h5.md"
|
"10.2.18-h5.md",
|
||||||
|
"10.2.18-h6.md"
|
||||||
],
|
],
|
||||||
"known": [
|
"known": [
|
||||||
"10.2.0.md",
|
"10.2.0.md",
|
||||||
|
|||||||
Reference in New Issue
Block a user