# node-fetch forwards secure headers to untrusted sites

Advisory record · `GHSA-r683-j2x4-v87g`

- **Identifiers:** `GHSA-r683-j2x4-v87g` · `CVE-2022-0235`
- **State:** Confirmed
- **Severity:** CVSS 8.8 High
- **Critical:** No
- **Weakness (CWE):** [CWE-173](https://cwe.mitre.org/data/definitions/173.html) · [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-601](https://cwe.mitre.org/data/definitions/601.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [Open redirect](https://agentprime.io/advisories/tag/open-redirect.md) · [CWE-173](https://agentprime.io/advisories/tag/cwe-173.md)
- **Published:** 21 Jan 2022
- **Updated:** 8 Nov 2023
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 21 Jan 2022, 23:55 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `node-fetch` (npm): affected `>=3.0.0, <3.1.1 || <2.6.7`; fixed in `3.1.1`, `2.6.7`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.8 High, CVSS 3.0: `CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from CNA (@huntrdev)

- **CISA KEV:** Not listed.
- **EPSS:** 0.017, the 76th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 21 Jan 2022. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-r683-j2x4-v87g](https://github.com/advisories/GHSA-r683-j2x4-v87g)
- [OSV: GHSA-r683-j2x4-v87g](https://osv.dev/vulnerability/GHSA-r683-j2x4-v87g)
- <https://nvd.nist.gov/vuln/detail/CVE-2022-0235>
- <https://github.com/node-fetch/node-fetch/pull/1449/commits/5c32f002fdd65b1c6a8f1e3620210813d45c7e60>
- <https://github.com/node-fetch/node-fetch/pull/1453>
- <https://github.com/node-fetch/node-fetch/commit/1ef4b560a17e644a02a3bfdea7631ffeee578b35>
- <https://github.com/node-fetch/node-fetch/commit/36e47e8a6406185921e4985dcbeff140d73eaa10>
- <https://github.com/node-fetch/node-fetch/commit/5c32f002fdd65b1c6a8f1e3620210813d45c7e60>
- <https://cert-portal.siemens.com/productcert/pdf/ssa-637483.pdf>
- <https://github.com/node-fetch/node-fetch>
- <https://huntr.dev/bounties/d26ab655-38d6-48b3-be15-f9ad6b6ae6f7>
- <https://lists.debian.org/debian-lts-announce/2022/12/msg00007.html>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-r683-j2x4-v87g>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-r683-j2x4-v87g/>. Everything for agents: <https://agentprime.io/llms.txt>.