How severe is CVE-2022-0536?

CVE-2022-0536 has a CVSS score of 2.6/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-0536?

CVE-2022-0536 affects the following packages: follow-redirects (npm). Ecosystems affected: npm.

How do I fix CVE-2022-0536?

Update follow-redirects to 1.14.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-0536 is resolved across your whole dependency graph.

How do I detect CVE-2022-0536 in my npm dependencies?

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.

How do I mitigate CVE-2022-0536 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 CVE-2022-0536 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-0536 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 CVE-2022-0536?

CVE-2022-0536 has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 71th 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.

What type of vulnerability is CVE-2022-0536?

CVE-2022-0536 is classified as CWE-212 (CWE-212). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-0536 published, and has it been updated?

CVE-2022-0536 was published on February 9, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

LOW severity

CVE-2022-0536 — follow-redirects

LOWFix: follow-redirects/follow-redirects@62e546a

CVE-2022-0536 is a low-severity (CVSS 2.6) CWE-212 vulnerability in follow-redirects. A fix is available for follow-redirects — see the affected versions and patch details below.

Improper Removal of Sensitive Information Before Storage or Transfer in follow-redirects/follow-redirects

Also known asGHSA-pw2r-vq6v-hr8c

Published

Feb 9, 2022

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs71th percentile — riskier than 71% of all scored CVEsHighest risk

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.

2Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

follow-redirectsnpm

143.4Mdownloads / week

Description

Improper Removal of Sensitive Information Before Storage or Transfer in NPM follow-redirects prior to 1.14.8.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`follow-redirects`	all versions	1.14.8`npm install follow-redirects@1.14.8`

Affected Products

1 product · 1 configurations

Application

follow-redirectsfollow-redirects_project

< 1.14.8

range

Detection & mitigation playbook

Open-source dependency

Detect
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.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-0536 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.

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.

Red HatModerate

Product	Fixed in	Advisory
OpenShift Service Mesh 2.1	`openshift-service-mesh/kiali-rhel8:1.36.9-1`	RHSA-2022:1739
Red Hat Migration Toolkit for Containers 1.7	`rhmtc/openshift-migration-ui-rhel8:v1.7.2-9`	RHSA-2022:5483
Red Hat OpenShift Data Foundation 4.11 on RHEL8	`odf4/odf-console-rhel8:v4.11.0-51`	RHSA-2022:6156
RHINT Service Registry 2.3.0 GA	`follow-redirects`	RHSA-2022:6835
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

UbuntuLOW

USN-8217-1Ubuntu

Frequently Asked Questions

Improper Removal of Sensitive Information Before Storage or Transfer in NPM follow-redirects prior to 1.14.8.

O3 Security · Impact-Aware SCA

Is CVE-2022-0536 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

2.6/10CVSS v3 base

Vector breakdown

Attack Vector

Adjacent

Attack Complexity

High

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Raw vector

CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N

CWE Classification

CWE-212CWE-212

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

follow-redirects

5.1/10

Code-Review0/10

Maintained5/10

Branch-Protection0/10

Assessed Oct 19, 2026

Timeline

Disclosed

Feb 9, 2022

Last updated

Oct 28, 2026

Identifiers

CVE-2022-0536

GHSA-pw2r-vq6v-hr8c

References

Advisorygithub.com · CVE 2022 0536.json Advisorynvd.nist.gov · CVE 2022 0536 Fixgithub.com · 62e546a99c07c3ee5e4e0718c84a6ca127c5c445 Webhuntr.dev · 7cf2bf90 52da 4d59 8028 a73b132de0db Packagegithub.com · follow redirects

Related vulnerabilities

Also affects follow-redirects

This CVE is low severity; 7 of 7 other CVEs affecting follow-redirects are rated as high or higher (top: high).

CVE-2026-116689CVE-2026-111755CVE-2026-111756CVE-2026-40895CVE-2024-28849CVE-2023-26159CVE-2022-0155

Same weakness: CWE-212

This CVE is low severity; 1 of 1 other CVE with CWE-212 is rated as high or higher (top: moderate).

GHSA-c8m5-c952-6cm4Browse all CWE-212

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2022-0536 — follow-redirects

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2022-0536 in your dependencies?