Disclaimer

Hotfix versions were inferred because the vendor did not list them explicitly: 10.2.13-h1, 10.2.13-h2, 10.2.13-h3, 10.2.13-h4, 10.2.13-h5, 10.2.13-h6, 10.2.13-h7, 10.2.13-h8, 10.2.13-h9, 10.2.13-h10, 10.2.13-h11, 10.2.13-h12, 10.2.13-h13, 10.2.13-h14, 10.2.13-h15, 10.2.13-h16, 10.2.13-h17, 10.2.16-h1, 10.2.16-h2, 10.2.16-h3, 10.2.16-h4, 10.2.16-h5, 11.1.6-h1, 11.1.6-h2, 11.1.6-h3, 11.1.6-h4, 11.1.6-h5, 11.1.6-h6, 11.1.6-h7, 11.1.6-h8, 11.1.6-h9, 11.1.6-h10, 11.1.6-h11, 11.1.6-h12, 11.1.6-h13, 11.1.6-h14, 11.1.6-h15, 11.1.6-h16, 11.1.6-h17, 11.1.6-h18, 11.1.6-h19, 11.1.6-h20, 11.1.10-h1, 11.1.10-h2, 11.1.10-h3, 11.1.10-h4, 11.1.10-h5, 11.1.10-h6, 11.2.4-h1, 11.2.4-h2, 11.2.4-h3, 11.2.4-h4, 11.2.4-h5, 11.2.4-h6, 11.2.4-h7, 11.2.4-h8, 11.2.4-h9, 11.2.4-h10, 11.2.4-h11, 11.2.4-h12, 11.2.4-h13, 11.2.7-h1, 11.2.7-h2, 11.2.7-h3

The earliest recollection of this bug is traced back to PAN-OS 10.2.13 - July 08, 2026. This bug is fixed in PAN-OS versions 10.2.16-h6, 11.1.10-h7, 11.1.14, 10.2.13-h18, 11.2.7-h4, 11.2.10, 11.1.6-h21, 10.2.18, 11.2.11, 11.1.13, 11.2.4-h14. Fixed an issue where, after upgrading, the Visible Virtual Systems field started to reference 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. Fixed an issue where, after upgrading to an affected PAN-OS release, the Visible Virtual Systems field started to reference 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. The wrong vsys is referenced under Visible Virtual System after every local firewall commit (auto-commit, commit, content install) if the display name of the vsys matches another vsys ID (for example, the vsys2 display name is vsys1). The incorrect vsys reference causes inter-vsys routing to fail. Workaround : Change the vsys display name so that it doesn't reference an existing vsys ID. 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. 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 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. 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. 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. For more information: https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-release-notes/pan-os-10-2-13-known-and-addressed-issues/pan-os-10-2-13-h18-addressed-issues https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-release-notes/pan-os-10-2-13-known-and-addressed-issues/pan-os-10-2-13-known-issues https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-release-notes/pan-os-10-2-16-known-and-addressed-issues/pan-os-10-2-16-h6-addressed-issues https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-release-notes/pan-os-10-2-16-known-and-addressed-issues/pan-os-10-2-16-known-issues https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-release-notes/pan-os-10-2-18-known-and-addressed-issues/pan-os-10-2-18-addressed-issues https://docs.paloaltonetworks.com/pan-os/11-1/pan-os-release-notes/pan-os-11-1-10-known-and-addressed-issues/pan-os-11-1-10-h7-addressed-issues https://docs.paloaltonetworks.com/pan-os/11-1/pan-os-release-notes/pan-os-11-1-13-known-and-addressed-issues/pan-os-11-1-13-addressed-issues https://docs.paloaltonetworks.com/pan-os/11-1/pan-os-release-notes/pan-os-11-1-14-known-and-addressed-issues/pan-os-11-1-14-addressed-issues https://docs.paloaltonetworks.com/pan-os/11-1/pan-os-release-notes/pan-os-11-1-6-known-and-addressed-issues/pan-os-11-1-6-h21-addressed-issues https://docs.paloaltonetworks.com/pan-os/11-2/pan-os-release-notes/pan-os-11-2-10-known-and-addressed-issues/pan-os-11-2-10-addressed-issues https://docs.paloaltonetworks.com/pan-os/11-2/pan-os-release-notes/pan-os-11-2-11-known-and-addressed-issues/pan-os-11-2-11-addressed-issues https://docs.paloaltonetworks.com/pan-os/11-2/pan-os-release-notes/pan-os-11-2-4-known-and-addressed-issues/pan-os-11-2-4-h14-addressed-issues https://docs.paloaltonetworks.com/pan-os/11-2/pan-os-release-notes/pan-os-11-2-4-known-and-addressed-issues/pan-os-11-2-4-known-issues https://docs.paloaltonetworks.com/pan-os/11-2/pan-os-release-notes/pan-os-11-2-7-known-and-addressed-issues/pan-os-11-2-7-h4-addressed-issues https://docs.paloaltonetworks.com/pan-os/11-2/pan-os-release-notes/pan-os-11-2-7-known-and-addressed-issues/pan-os-11-2-7-known-issues