[
  {
    "id": "PANG-11201",
    "summary": "On Prisma Access Agents for Linux, when NetworkManager is configured not to manage the tunnel interface, the Prisma Access Agent connection profile becomes stuck in an \"activating\" state, resulting in a tunnel connect and disconnect loop that prevents successful establishment of the tunnel.",
    "resolved": "Resolved in Prisma Access Agent 26.1.1",
    "caveat": "",
    "renderedHtml": "<div><strong>Resolved:</strong> Resolved in Prisma Access Agent 26.1.1</div><p>On Prisma Access Agents for Linux, when NetworkManager is configured not to manage the tunnel interface, the Prisma Access Agent connection profile becomes stuck in an \"activating\" state, resulting in a tunnel connect and disconnect loop that prevents successful establishment of the tunnel.</p>\n"
  },
  {
    "id": "PANG-11153",
    "summary": "On Linux, the Prisma Access Agent may experience recurring PASrv process crashes approximately every 20 seconds due to abnormal termination, causing the agent to become unresponsive and preventing log collection. This issue occurs primarily during agent upgrade operations.",
    "resolved": "Resolved in Prisma Access Agent 26.1.1",
    "caveat": "",
    "renderedHtml": "<div><strong>Resolved:</strong> Resolved in Prisma Access Agent 26.1.1</div><p>On Linux, the Prisma Access Agent may experience recurring PASrv process crashes approximately every 20 seconds due to abnormal termination, causing the agent to become unresponsive and preventing log collection. This issue occurs primarily during agent upgrade operations.</p>\n"
  },
  {
    "id": "PANG-10947",
    "summary": "When Prisma Access Agent is configured in on-demand mode on Arch Linux and the network connection is interrupted and then restored, the agent fails to automatically reconnect to the gateway. As a result, the agent remains in a disconnected state.",
    "resolved": "",
    "caveat": "",
    "renderedHtml": "<p>When Prisma Access Agent is configured in on-demand mode on Arch Linux and the network connection is interrupted and then restored, the agent fails to automatically reconnect to the gateway. As a result, the agent remains in a disconnected state.</p>\n"
  },
  {
    "id": "PANG-10865",
    "summary": "On Prisma Access Agent for Linux systems, the Prisma Access Agent user interface exhibits minor cosmetic and usability inconsistencies. The Location list lacks a line separator between entries and is not sorted alphabetically, with the exception of the \"Best Location\" option.",
    "resolved": "",
    "caveat": "",
    "renderedHtml": "<p>On Prisma Access Agent for Linux systems, the Prisma Access Agent user interface exhibits minor cosmetic and usability inconsistencies. The Location list lacks a line separator between entries and is not sorted alphabetically, with the exception of the \"Best Location\" option.</p>\n"
  },
  {
    "id": "PANG-10801",
    "summary": "During a Host Information Profile (HIP) check on Prisma Access Agent for Linux, the system incorrectly validates certificates based solely on the issuer's Common Name (CN). This results in expired or revoked certificates being considered valid if their issuer's CN matches the configured criteria, potentially allowing non-compliant endpoints to pass HIP checks.",
    "resolved": "",
    "caveat": "",
    "renderedHtml": "<p>During a Host Information Profile (HIP) check on Prisma Access Agent for Linux, the system incorrectly validates certificates based solely on the issuer's Common Name (CN). This results in expired or revoked certificates being considered valid if their issuer's CN matches the configured criteria, potentially allowing non-compliant endpoints to pass HIP checks.</p>\n"
  },
  {
    "id": "PANG-10668",
    "summary": "After upgrading to Prisma Access Agent version 26.1.0.25 on Arch Linux with KDE Plasma desktop environments, the settings page in the Prisma Access Agent app might appear partially blank when the operating system's dark theme is enabled. This prevents the display of relevant information on the settings page.",
    "resolved": "",
    "caveat": "",
    "renderedHtml": "<p>After upgrading to Prisma Access Agent version 26.1.0.25 on Arch Linux with KDE Plasma desktop environments, the settings page in the Prisma Access Agent app might appear partially blank when the operating system's dark theme is enabled. This prevents the display of relevant information on the settings page.</p>\n"
  },
  {
    "id": "PANG-9501",
    "summary": "When using Prisma Access Agent on a system running Fedora 42 (GNOME), running the `pacli traffic log <n>` command does not show the log details.",
    "resolved": "",
    "caveat": "",
    "renderedHtml": "<p>When using Prisma Access Agent on a system running Fedora 42 (GNOME), running the <code>pacli traffic log &lt;n&gt;</code> command does not show the log details.</p>\n"
  },
  {
    "id": "PANG-9196",
    "summary": "When Prisma Access Agent is installed on a Linux virtual machine (VM) running on an ESXi host, and the VM undergoes network changes (such as connecting or disconnecting from gateways) or experiences a sleep/wake cycle, the entire VM and the ESXi host might become unresponsive. Access to the ESXi host is lost, and the system hangs for approximately 5 minutes before access is regained.",
    "resolved": "",
    "caveat": "",
    "renderedHtml": "<p>When Prisma Access Agent is installed on a Linux virtual machine (VM) running on an ESXi host, and the VM undergoes network changes (such as connecting or disconnecting from gateways) or experiences a sleep/wake cycle, the entire VM and the ESXi host might become unresponsive. Access to the ESXi host is lost, and the system hangs for approximately 5 minutes before access is regained.</p>\n"
  }
]