NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
CRITICAL severity

Server-Side Request Forgery (SSRF) in GitHub repository ionicabizau/parse-urlGHSA-j9fq-vwqv-2fm2

CRITICALFix: ionicabizau/parse-url@b88c81d

GHSA-j9fq-vwqv-2fm2 is a critical-severity (CVSS 9.1) Server-Side Request Forgery (SSRF) 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.

Also known asCVE-2022-2900
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs69th percentile — riskier than 69% of all scored CVEsHighest risk
0.00%0.58%1.16%1.74%0.4%1.2%May 26Sep 26Nov 26

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

1 pkg affected

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.

462other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
parse-urlnpm
6.8Mdownloads / week

Description

Server-Side Request Forgery (SSRF) in GitHub repository ionicabizau/parse-url prior to 8.1.0.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmparse-urlall versions8.1.0npm install parse-url@8.1.0

Affected Products

1 product · 1 configurations
Application
parse-urlparse-url_project
< 8.1.0
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Server-Side Request Forgery (SSRF) in GitHub repository ionicabizau/pars…

huntr.devNVDSep 2022

Detection & mitigation playbook

Open-source dependency

  1. Detect

    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.

  2. Fix

    Update parse-url to 8.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j9fq-vwqv-2fm2 is resolved across your whole dependency graph.

  3. Workarounds

    Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

Server-Side Request Forgery (SSRF) in GitHub repository ionicabizau/parse-url prior to 8.1.0.
O3 Security · Impact-Aware SCA

Is GHSA-j9fq-vwqv-2fm2 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Server-Side Request Forgery (SSRF) in GitHub repository…