Threats / Palo Alto Networks / CVE-2024-5910
CVE-2024-5910
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Palo Alto Networks Expedition vulnerability
Palo Alto Networks Expedition lacks authentication controls, allowing network-accessible attackers to assume admin accounts and access configuration secrets and credentials.
Verdict
Today item — known-exploited.
Missing authentication in Expedition enables unauthorized administrative takeover by network-adjacent threat actors, exposing sensitive configuration data and credentials to compromise.
CISA KEV Yes · 2024-11-075EPSS 0.91783 (verify live)6Exploit Weaponized · public PoC7CVSS 9.33CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
16 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-11-07).
Probability (EPSS)
EPSS 0.91783 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.3 (CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L/AU:Y/R:U/V:D/RE:M/U:Red) · Affected: Palo Alto Networks, Expedition. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 4.0, set at disclosure.
Weakness (CWE)
Mapped to CWE-306 Missing Authentication — weakness family: Authentication.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 120 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module, nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I gain network access to an Expedition instance and bypass authentication to reach admin functions.
Business
Administrative access is compromised without credential validation, eliminating a critical security boundary.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I assume control of an admin account and extract configuration secrets and stored credentials from the system.
Business
Sensitive credentials and network configuration data are exposed to unauthorized parties, enabling lateral movement.
3
Lateral reach — past segmentation narrative 3
Attacker
I leverage extracted credentials to access downstream systems and infrastructure managed through Expedition.
Business
Compromise cascades across the security infrastructure, amplifying the scope of the breach beyond Expedition itself.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by palo_altoCNA
Credited with finding itBrian Hysell (Synopsys CyRC)finder