The private_address_check ruby gem before 0.4.1 is vulnerable to a bypass due to an incomplete blacklist of common private/local network addresses used to prevent server-side request forgery.
Loading...
Loading...
This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 43% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
The private_address_check ruby gem before 0.4.1 is vulnerable to a bypass due to an incomplete blacklist of common private/local network addresses used to prevent server-side request forgery.
November 16, 2017
May 13, 2026
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| private_address_check | 0.1.0, 0.2.0, 0.3.0, 0.4.0 | 0.4.1 | — |
Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.
See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-0909
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.