Skip to content
vulnerability

CVE-2024-5910

9.8
Critical
KEV · Exploited in wildEPSS 92%Patch available

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. Configuration secrets, credentials, and other data imported into Expedition is at risk due to this issue.

exploited
Yes, in CISA KEV since 7 Nov 2024fix by 28 Nov 2024 (CISA deadline for US federal agencies)public exploit code
fix
Patch available see the advisory in the references
likelihood
EPSS 91.7%
Published 10 Jul 2024Analysed here 2 Nov 2026

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

triage
server-sideruntimeWAF can block: noAV · networkCWE-306· Missing Authentication

Can a WAF block it? No. The vulnerability involves missing authentication for a critical function accessible to attackers with network access, but the description does not specify HTTP or web requests. Therefore, it is not clear if a web application firewall could filter the attack.

Also consider: patch

Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectornetworkattack complexitylowprivileges requirednoneuser interactionnonescopeunchangedconfidentialityhighintegrityhighavailabilityhigh
CVSS 3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
common questions

Is CVE-2024-5910 being exploited?

Yes. CVE-2024-5910 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2024-5910?

CVE-2024-5910 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2024-5910?

Yes. A fix has been recorded for CVE-2024-5910. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2024-5910 affect?

CVE-2024-5910 affects paloaltonetworks:expedition. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
paloaltonetworks:expedition
affected versions
Palo Alto Networks Expedition
  • affected>= 1.2 and < 1.2.92

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

public exploits

Public exploit code: 1 on Exploit-DB · 1 Metasploit module · 1 Nuclei template

Metasploit
Nuclei

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

cisa ssvc

exploitation
active
automatable
yes
technical impact
total

Assessed by CISA 7 Nov 2024 (SSVC 2.0.3).

timeline

  1. 10 Jul 2024Published
  2. 7 Nov 2024Added to CISA KEV (exploited in the wild) · 119 days (about 4 months) later
  3. 7 Nov 2024CISA SSVC assessment: exploitation active · same day later
  4. 28 Nov 2024CISA remediation due date (US federal agencies) · 21 days later
  5. 6 Apr 2025First public exploit or proof of concept · 129 days (about 4 months) later
  6. 21 Oct 2025CVE record last updated · 199 days (about 7 months) later
  7. 2 Nov 2026Analysed by vulneraibility.com · 377 days (about 1 year) later
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
3 references in the CVE record: 1 advisory, 2 links

sources

get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved