⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Critical · CVSS 9.3 ⚠ ACTIVELY EXPLOITED — CISA KEV

How to Fix CVE-2024-5910: Authentication Bypass in Expedition

Other vulnerabilities in the same area that are worth patching alongside this one:

*By Sai Kiran Pandrala*

⚡ At a glance
SeverityCVSS 9.3 - Critical
Actively exploited?Yes, listed in CISA KEV (added 2024-11-07)
Affected1.2 < 1.2.92
Fixed inSee vendor advisory
Type (CWE)CWE-306: Missing Authentication for Critical Function
Patch immediately. CISA's KEV listing means active exploitation is confirmed. Federal agencies must remediate by 2024-11-28.

What is CVE-2024-5910?

CVE-2024-5910 is an authentication bypass in Expedition. A flaw in the authentication or session-handling logic lets a remote attacker reach administrative functions without valid credentials. In several reported cases this leads directly to remote code execution. Vendor description: Missing authentication for a critical function in Palo Alto Networks Expedition can lead to an Expedition admin account takeover for attackers with network access to Expedition. Note: Expedition is a tool aiding in configuration migration, tuning, and enrichment.

Why this CVE matters

Authentication bypass on a network appliance or admin console is a top-tier target. Once the attacker is past the login, every administrative endpoint becomes available, including the ones that change settings, upload firmware, or run shell commands.

For deployments of Expedition that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Confirmed in-the-wild exploitation makes that assumption mandatory, not cautious. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

On PAN-OS, run show system info | match sw-version from the CLI, or read the Dashboard widget in the GUI.

How to fix CVE-2024-5910

  1. Read the vendor advisory in full: https://security.paloaltonetworks.com/CVE-2024-5910
  2. Upgrade Expedition to the patched build listed in the vendor advisory.
  3. Back up the configuration (and database, where applicable) before upgrading.
  4. Rotate any credentials, API keys, or session tokens that the vulnerable service touched. An unauthenticated RCE-class flaw means anything the process could see should be treated as exposed.
  5. Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
  6. Restart the affected service so the patched binary loads, then verify the new version (see verification section).

Upgrade PAN-OS to the patched release


# Target PAN-OS build 1.2.92.
show system info | match sw-version

request system software download version 1.2.92
request system software install version 1.2.92
request restart system

# Post-reboot verification
show system info | match sw-version

Verify the fix landed


# 1. Confirm the running version matches the fixed-in version from the advisory:
#    https://security.paloaltonetworks.com/CVE-2024-5910
#    Use the platform-specific version probe above.

# 2. Re-scan with your vulnerability scanner (Nessus, Qualys, Tenable, OpenVAS).
#    The scanner should no longer flag CVE-2024-5910 on the patched target.

# 3. Inspect recent service / kernel logs for crash loops or rollback events.
journalctl -u <service> --since "10 minutes ago"
dmesg --since "10 minutes ago"

If you cannot patch immediately

Restrict access to the affected administrative interface to trusted internal networks. Disable the vulnerable component if the vendor documents that as an interim option. Patch immediately when feasible.

How to verify the fix worked

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for unexpected administrator accounts in Expedition, scheduled tasks or cron jobs you did not create, new files in web-accessible directories, and outbound connections to addresses not in your baseline. Suspicious requests to the vulnerable endpoint immediately followed by successful 200-class responses with unusually large bodies are a strong indicator of exploitation. Because Expedition sits on CISA's Known Exploited Vulnerabilities catalog for this CVE, defenders should also pull the IOC list from the vendor advisory and from CISA's analysis if one was published.

Frequently asked questions

Is CVE-2024-5910 being exploited in the wild?

Yes. CISA added CVE-2024-5910 to the Known Exploited Vulnerabilities catalog, which means active exploitation has been confirmed by federal observation or credible vendor reporting.

Will a WAF or IDS rule fully mitigate CVE-2024-5910?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

Do I need to assume compromise if my Expedition was internet-facing and unpatched?

For an unauthenticated RCE-class flaw exposed to the public internet during the known exploitation window, yes. Review logs, rotate credentials the process could access, and look for unexpected accounts, scheduled tasks, or outbound connections.

References

*This guide was assembled from the official vendor advisory, the NVD record, and the CISA KEV catalog entry on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*