CVE-2022-0155 is a high-severity (CVSS 8) CWE-359 vulnerability in follow-redirects. 1 public exploit reference exists, so weaponization risk is real. A fix is available for follow-redirects — see the affected versions and patch details below.
Exposure of Private Personal Information to an Unauthorized Actor in follow-redirects/follow-redirects
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2022-0155 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
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.
follow-redirectsnpmDescription
follow-redirects is vulnerable to Exposure of Private Personal Information to an Unauthorized Actor
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | follow-redirects | all versions | 1.14.7npm install follow-redirects@1.14.7 |
Research 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 follow-redirects, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update follow-redirects to 1.14.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-0155 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-0155 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2022-0155. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
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 |
|---|---|---|
| Red Hat Virtualization Engine 4.4 | ovirt-web-ui-0:1.9.2-1.el8ev | RHSA-2022:8502 |
| Red Hat Openshift Data Foundation 4.14 | odf4/cephcsi-rhel9:v4.14-1764178221 | RHSA-2025:22420 |
| Red Hat Openshift Data Foundation 4.15 | odf4/cephcsi-rhel9:v4.15-1764176261 | RHSA-2025:22418 |
| Red Hat Openshift Data Foundation 4.16 | odf4/cephcsi-rhel9:v4.16-1764168955 | RHSA-2025:22416 |
| Red Hat Openshift Data Foundation 4.17 | odf4/cephcsi-rhel9:v4.17-1764167834 | RHSA-2025:22415 |
| Red Hat Openshift Data Foundation 4.18 | odf4/cephcsi-rhel9:v4.18-1761854289 | RHSA-2025:21368 |
| Red Hat Openshift Data Foundation 4.19 | odf4/cephcsi-rhel9:v4.19-1761844221 | RHSA-2025:21378 |
| Red Hat Openshift Data Foundation 4.20 | odf4/cephcsi-rhel9:v4.20-1761848902 | RHSA-2025:21704 |
Frequently Asked Questions
Is CVE-2022-0155 in your dependencies?
O3 Security finds CVE-2022-0155 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.