Skip to main content
Mallory
MediumVulnerability

CVE-2025-0106: Wildcard expansion file enumeration in Palo Alto Networks Expedition

Published Jan 11, 2025 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS6.9Medium · v4
EPSS0.47%41st percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Palo Alto Networks
IdentifiersCVE-2025-0106CWE-73

CVE-2025-0106 is a wildcard expansion vulnerability in Palo Alto Networks Expedition affecting versions earlier than 1.2.101. The flaw allows an unauthenticated attacker to abuse wildcard expansion behavior to enumerate files on the underlying host filesystem. In the context of Expedition, this can expose knowledge of files present on the system and may aid follow-on targeting of sensitive application data stored by the migration tool, including firewall-related configuration material and secrets handled by the platform.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows unauthenticated disclosure of filesystem metadata through file enumeration on the host running Expedition. While the reported direct impact is information disclosure rather than code execution, the exposed knowledge can help an attacker identify sensitive files and application artifacts for subsequent attacks. Because Expedition may store firewall credentials, configuration settings, and API keys, filesystem visibility can materially increase the risk of broader compromise.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, restrict all unnecessary network access to Expedition, especially unauthenticated exposure, and limit access to trusted administrative networks only. Reduce the sensitivity of data stored on the host where possible, review filesystem permissions available to the web application environment, and monitor for suspicious requests indicative of filesystem probing. Long term, replace unsupported Expedition deployments with supported alternatives.

Remediation

Patch, then assume compromise.

Upgrade Palo Alto Networks Expedition to version 1.2.101 or later, which contains the vendor's fixes for the affected vulnerabilities. Because Expedition reached end of technical support on 2024-12-31, migration to a supported replacement product should also be prioritized.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Palo Alto NetworksExpeditionapplication
FAQ

Frequently asked questions

Is CVE-2025-0106 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2025-0106 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-0106?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2025-0106.
Is there a patch for CVE-2025-0106?
Upgrade Palo Alto Networks Expedition to version 1.2.101 or later, which contains the vendor's fixes for the affected vulnerabilities. Because Expedition reached end of technical support on 2024-12-31, migration to a supported replacement product should also be prioritized.
What products are affected by CVE-2025-0106?
Palo Alto Networks Expedition.
How severe is CVE-2025-0106?
CVE-2025-0106 has a CVSS v4 score of 6.9 (Medium) and an EPSS score of 0.47% (41st percentile) as of Sep 25, 2026.
Activity feed

Recent activity

1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.