Actively exploited

CVE-2024-3393 Palo Alto Networks PAN-OS Malicious DNS Packet Vulnerability

Palo Alto Networks PAN-OS contains a vulnerability in parsing and logging malicious DNS packets in the DNS Security feature that, when exploited, allows an unauthenticated attacker to remotely reboot the firewall. Repeated attempts to trigger this condition will cause the firewall to enter maintenance mode.

From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.

Our Assessment

Should You Worry?

Patch nowCybergen assessment
  • CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 30 Dec 2024.
  • Rated High severity (CVSS 7.1, scored by Vendor).
  • This product type is often exposed to the internet, which is where attackers scan for it first.
  • It has been in the catalogue for 676 days. Systems still unpatched now have almost certainly been scanned for it.
The Vulnerability

What It Is

A Denial of Service vulnerability in the DNS Security feature of Palo Alto Networks PAN-OS software allows an unauthenticated attacker to send a malicious packet through the data plane of the firewall that reboots the firewall. Repeated attempts to trigger this condition will cause the firewall to enter maintenance mode.

Affected Versions

ProductVersions
Palo Alto Networks Cloud NGFWSee the vendor advisory
Palo Alto Networks PAN-OS11.2.0 to before 11.2.3
11.1.0 to before 11.1.2-h16
10.2.8 to before 10.2.8-h19
10.1.14 to before 10.1.14-h8
Palo Alto Networks PAN-OS11.2.0 to before 11.2.3

From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.

From Watch to Action

What To Do Now

  1. 1

    Find it

    Search your asset inventory and external attack surface for Palo Alto Networks PAN-OS. Include cloud images, appliances and anything a supplier runs for you.

    Attack Surface Management
  2. 2

    Fix it

    Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

    Vulnerability Management
  3. 3

    Hunt for compromise

    If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.

    Incident Response
  4. 4

    Prove it is fixed

    Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.

    Penetration Testing

Not Sure If You Are Exposed?

Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2024-3393 and every other exploited flaw on the list.

Check My Exposure