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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

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.

How does O3 Security protect against CVE-2022-0536?

O3 pinpoints whether CVE-2022-0536 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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.

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 July 15, 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

CVE-2022-0536

LOW

CVE-2022-0536 is a low-severity (CVSS 2.6) vulnerability in follow-redirects. O3 Security confirms whether CVE-2022-0536 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

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

Jul 15, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

follow-redirectsnpm

101.9Mdownloads / 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

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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.
How O3 protects you
O3 pinpoints whether CVE-2022-0536 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2022-0536. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 detects CVE-2022-0536 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works