What is CVE-2024-9465?

CVE-2024-9465 is Expedition: SQL Injection Leads to Firewall Admin Credential Disclosure. The supplied enrichment data classifies it as Injection mapped to CWE-89 SQL Injection.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Is there a public exploit?

1 public PoC repositories reported; 0 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS, database audit logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2024-9465 using CVSS 9.1, EPSS 100%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

Workarounds are not confirmed from current sources. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVcriticalInjectionpublic exploit

CVE-2024-9465

CVE-2024-9465 — Expedition: SQL Injection Leads to Firewall Admin Credential Disclosure

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2024-9465 in CISA KEV with required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

An SQL injection vulnerability in Palo Alto Networks Expedition allows an unauthenticated attacker to reveal Expedition database contents, such as password hashes, usernames, device configurations, and device API keys. With this, attackers can also create and read arbitrary files on the Expedition system.

Published Oct 9, 2024Updated Jun 17, 2026Sources: NVD, Palo Alto Networks (CNA), CISA, FIRST EPSS

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Nov 14, 2024

EPSS

100%

top of FIRST's scoreset

Affects

Palo Alto

Expedition

CVSS base

9.1

critical · 2 sources

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

Yes

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

The fixes for all listed issues are available in Expedition 1.2.96, and all later Expedition versions. All Expedition usernames, passwords, and API keys should be rotated after upgrading to the fixed version of Expedition. All firewall usernames, passwords, and API keys processed by Expedition should be rotated after updating.

CISA required action

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

Federal deadline Dec 5, 2024 — passed 648 days ago

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
Palo Alto	Expedition	1.2.0 to < 1.2.96	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

None

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
9.1	CVSS 3.1	critical	3.9	5.2	NVD
9.2	CVSS 4.0	critical	—	—	Palo Alto Networks (CNA)

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Weakness & attack patterns

CWE-89SQL Injection

Inferred from the weakness class — not observed against this CVE.

CAPEC-66 · SQL InjectionCAPEC-7 · Blind SQL Injection

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Nov 14, 2024

Federal deadline

Dec 5, 2024

passed 648 days ago

Ransomware use

Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Exploit entries

Exploit-DB and CTI exploit indexes

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable Expedition.
Monitor for scanner or exploit-pattern traffic after 1 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPSdatabase audit logs

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 9.1 (AV:N)
Jun 17, 2026 · NVD
2024
Added to CISA KEV catalog
Nov 14, 2024 · CISA
Initial · CVE published
Oct 9, 2024 · NVD
Reported · Initial publication
Oct 9, 2024 · Palo Alto Networks

References

4 on the record

security.paloaltonetworks.com/PAN-SA-2024-0010
Mitigation, Vendor Advisory
www.horizon3.ai/attack-research/palo-alto-expedition-from-n-day-to-full-compromise/
Exploit
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-9465
US Government Resource
nvd.nist.gov/vuln/detail/CVE-2024-9465
Vendor Advisory

Elsewhere on this site

Palo Altoevery CVE for this vendor
November 2024what else CISA listed
Injectionsame class
CWE-89other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2024-9465 is Expedition: SQL Injection Leads to Firewall Admin Credential Disclosure, a critical vulnerability affecting Expedition from Palo Alto Networks. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 1 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 9.1 describes technical severity, while EPSS 100% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.