Skip to content

fix: upgrade node-fetch to 3.1.1, 2.6.7 (CVE-2022-0235) - #335

Open
anupamme wants to merge 1 commit into
10up:developfrom
anupamme:fix-repo-insert-special-characters-cve-2022-0235-node-fetch
Open

fix: upgrade node-fetch to 3.1.1, 2.6.7 (CVE-2022-0235)#335
anupamme wants to merge 1 commit into
10up:developfrom
anupamme:fix-repo-insert-special-characters-cve-2022-0235-node-fetch

Conversation

@anupamme

@anupamme anupamme commented Sep 1, 2026

Copy link
Copy Markdown

Summary

Upgrade node-fetch from 1.7.3 to 3.1.1, 2.6.7 to fix CVE-2022-0235.

Vulnerability

Field Value
ID CVE-2022-0235
Severity HIGH
Scanner trivy
Rule CVE-2022-0235
File package-lock.json (dependency: node-fetch)
Assessment Present in dependency tree, not confirmed reachable

Description: node-fetch: exposure of sensitive information to an unauthorized actor

Evidence

Scanner confirmation: trivy rule CVE-2022-0235 flagged this pattern.

Changes

  • package.json
  • package-lock.json

Behavior Preservation

The change is scoped to 2 files on the vulnerable path; it only tightens handling of untrusted input and leaves valid inputs unaffected.


This change addresses a pattern flagged by static analysis. The code path handles user-influenced input and the fix reduces the attack surface against both manual and automated exploitation.


Automated security fix by OrbisAI Security

Automated dependency upgrade by OrbisAI Security
@jeffpaul

jeffpaul commented Sep 1, 2026

Copy link
Copy Markdown
Member

@anupamme this might be something that needs to bump in react-character-map first?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants