CVE-2024-25466 is a high-severity (CVSS 7.3) CWE-26 vulnerability in react-native-document-picker. A fix is available for react-native-document-picker — see the affected versions and patch details below.
React Native Document Picker Directory Traversal vulnerability
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-25466.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
react-native-document-pickernpmDescription
Directory Traversal vulnerability in React Native Document Picker before v.9.1.1 and fixed in v.9.1.1 allows a local attacker to execute arbitrary code via a crafted script to the Android library component.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | react-native-document-picker | ≥ 9.0.0&&< 9.1.1 | 9.1.1npm install react-native-document-picker@9.1.1 |
| 📦npm | react-native-document-picker | all versions | 8.2.2npm install react-native-document-picker@8.2.2 |
Affected Products
document pickerreact-native-documentsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for react-native-document-picker, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update react-native-document-picker to 9.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-25466 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
Frequently Asked Questions
Is CVE-2024-25466 in your dependencies?
Find it across npm, including transitive dependencies.