CVE-2022-26260 is a critical-severity (CVSS 9.8) CWE-1321 vulnerability in simple-plist. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for simple-plist — see the affected versions and patch details below.
Prototype Pollution in simple-plist
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, and reverse-dependency count shows how many other packages break if it stays unpatched.
simple-plistnpmDescription
Simple-Plist v1.3.0 was discovered to contain a prototype pollution vulnerability via .parse().
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | simple-plist | all versions | 1.3.1npm install simple-plist@1.3.1 |
Affected Products
simple-plistsimple-plist_projectResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for simple-plist, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update simple-plist to 1.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-26260 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2022-26260 in your dependencies?
Find it across npm, including transitive dependencies.