How severe is GHSA-x2xg-6wcj-6xf9?

GHSA-x2xg-6wcj-6xf9 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-x2xg-6wcj-6xf9?

GHSA-x2xg-6wcj-6xf9 affects the following packages: vanilla/safecurl (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-x2xg-6wcj-6xf9?

Update vanilla/safecurl to 0.9.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x2xg-6wcj-6xf9 is resolved across your whole dependency graph.

How do I detect GHSA-x2xg-6wcj-6xf9 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vanilla/safecurl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-x2xg-6wcj-6xf9 if there is no patch (or I can't update yet)?

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.

Is GHSA-x2xg-6wcj-6xf9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-x2xg-6wcj-6xf9 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-x2xg-6wcj-6xf9?

GHSA-x2xg-6wcj-6xf9 has an EPSS (Exploit Prediction Scoring System) score of 1.8%, placing it in the 78th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-x2xg-6wcj-6xf9 published, and has it been updated?

GHSA-x2xg-6wcj-6xf9 was published on August 25, 2021 and was last updated on December 2, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

CRITICAL severity

SafeCurl before 0.9.2 has a DNS rebinding vulnerabilityGHSA-x2xg-6wcj-6xf9

CRITICALFix: vanilla/safecurl#2

GHSA-x2xg-6wcj-6xf9 is a critical-severity (CVSS 9.8) vulnerability in vanilla/safecurl. A fix is available for vanilla/safecurl — see the affected versions and patch details below.

Also known asCVE-2020-36474

Published

Aug 25, 2021

Updated

Dec 2, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 12, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs78th percentile — riskier than 78% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-x2xg-6wcj-6xf9 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

🐘vanilla/safecurl

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

SafeCurl before 0.9.2 has a DNS rebinding vulnerability.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`vanilla/safecurl`	all versions	0.9.2`composer require vanilla/safecurl:^0.9.2`

Affected Products

1 product · 1 configurations

Application

safecurlsafecurl_project

1 version

0.9.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vanilla/safecurl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update vanilla/safecurl to 0.9.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x2xg-6wcj-6xf9 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

SafeCurl before 0.9.2 has a DNS rebinding vulnerability.

O3 Security · Impact-Aware SCA

Is GHSA-x2xg-6wcj-6xf9 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works