Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Inquiry about lodash dependency updates

Open
#1,023 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, node.js
Domain
backend, security

Research direction

Start by reviewing PR #1022 and the dependency chain through cf-nodejs-logging-support@7.4.5 to jsonwebtoken@9.0.3. Check the PR discussion and release information for the lodash vulnerability updates, then confirm the current status, blockers, and whether a release timeline is documented.

Written by the indexing model from the issue text.

Description

Summary

We're downstream users of jsonwebtoken (via cf-nodejs-logging-support) and noticed PR #1022 addressing lodash vulnerabilities. Would appreciate any information about the status of this PR.

Impact

Our security scans flag jsonwebtoken@9.0.3 due to vulnerable lodash sub-packages including lodash.includes, lodash.isnumber, lodash.isboolean, etc.

CVEs:

  • CVE-2026-4800 (CVSS 9.8) - Command Injection
  • CVE-2019-10744 (CVSS 9.1) - Prototype Pollution
  • CVE-2021-23337 (CVSS 7.2) - Command Injection
  • CVE-2020-8203 (CVSS 7.4) - Prototype Pollution

Question

If possible, could you share:

  1. Any updates on PR #1022?
  2. Approximate timeline for a release?
  3. Whether there's anything blocking progress that we might help with?

We're available to help with testing if useful.

Context

  • Dependency chain: Our app → cf-nodejs-logging-support@7.4.5 → jsonwebtoken@9.0.3

References

  • PR #1022
Dominant language
JavaScript
Stars
18.2k
Forks
1.3k
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from auth0/node-jsonwebtoken

All issues in auth0/node-jsonwebtoken

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.