CVE-2022-0722 is a medium-severity (CVSS 4.8) Information Exposure vulnerability in parse-url. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for parse-url — see the affected versions and patch details below.
Exposure of Sensitive Information to an Unauthorized Actor in ionicabizau/parse-url
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.
parse-urlnpmDescription
Exposure of Sensitive Information to an Unauthorized Actor via hostname confusion in GitHub repository ionicabizau/parse-url prior to 6.0.1
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | parse-url | all versions | 6.0.1npm install parse-url@6.0.1 |
Affected Products
parse-urlparse-url_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 parse-url, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update parse-url to 6.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-0722 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| RHPAM 7.13.1 async | parse-url | RHSA-2022:6813 |
Frequently Asked Questions
Is CVE-2022-0722 in your dependencies?
Find it across npm, including transitive dependencies.