ExpeditionApplication · Paloaltonetworks
CVE-2025-0106
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA wildcard expansion vulnerability in Palo Alto Networks Expedition allows an unauthenticated attacker to enumerate files on the host filesystem.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA wildcard expansion vulnerability in Palo Alto Networks Expedition allows an unauthenticated attacker to enumerate files on the host filesystem by exploiting wildcard character expansion in file path handling.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ExpeditionApplication
< 1.2.101CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Expedition installation and versionLocate the Expedition application and check its version number. This is typically visible in the web UI login page, in the application itself under 'About' or 'Settings', or via command line if you have shell access to the host.Affected if The installed version is lower than 1.2.101
-
Confirm Expedition web interface is network-accessibleVerify whether the Expedition web interface (typically on ports 443 or 8080) is reachable from network locations outside the trusted administrative network. Attempt a curl or browser request to the interface from an external host.Affected if The interface is exposed to untrusted networks, allowing unauthenticated access
-
Check for wildcard-based file access attempts in logsReview Expedition server logs (typically stored in /var/log/ or within the application logs directory) for entries containing wildcard characters (* or ?) in file path parameters. Look for repeated requests to path-related endpoints.Affected if Logs show wildcard expansion attempts or anomalous file path requests from unauthenticated sources
-
Verify authentication is required for file-related endpointsTest file-related API endpoints or pages by accessing them without credentials. Attempt to access paths that might use wildcard expansion (e.g., paths with * or ? characters) without providing authentication tokens.Affected if Unauthenticated requests to file-related endpoints succeed or return unexpected file listings
The environment is affected if Palo Alto Expedition version is below 1.2.101 AND the web interface is accessible to untrusted network segments, enabling unauthenticated wildcard-based file enumeration.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.2.101
Apply vendor-supplied patch when available; until then, restrict network access to the Expedition interface to minimize exposure.
1.2.101
- Upgrade Palo Alto Networks Expedition to version 1.2.101 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Expedition
Scoped from the published advisory
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0106 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-0106 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data