Visitar URL original
Vulnerability in dependencies "minimatch" <10.2.1 · Issue #2267 · remy/nodemon · GitHub
Skip to content

Vulnerability in dependencies "minimatch" <10.2.1 #2267

Closed

Description

@danwater

minimatch <10.2.1
Severity: high
minimatch has a ReDoS via repeated wildcards with non-matching literal in pattern - GHSA-3ppc-4f35-3m26

It appears that this application depends on "minimatch" 3.1.2 which is now listed as having a known vulnerability. I did try overriding the package to the fixed version but the API has changed and breaks functionality.

See above for the advisory and CVE: CVE-2026-26996

Activity

  1. added 2 commits that reference this issue on Feb 19, 2026
    e089516
    9376af3
  2. remy commented on Feb 19, 2026

    @remy
    Owner

    bump going up in the next release

  3. lkraav commented on Mar 21, 2026

    @lkraav

    This missed bumping engine requirements to Node 18+, because now on Node 16, nodemon-3.1.12+ won't install, breaking reasonable ^ constraints like ^3.1.11.

    $ npm --workspaces=false install --package-lock-only
    npm ERR! code EBADENGINE
    npm ERR! engine Unsupported engine
    npm ERR! engine Not compatible with your version of node/npm: minimatch@10.2.4
    npm ERR! notsup Not compatible with your version of node/npm: minimatch@10.2.4
    npm ERR! notsup Required: {"node":"18 || 20 || >=22"}
    npm ERR! notsup Actual:   {"npm":"8.19.4","node":"v16.20.2"}
    
    npm ERR! A complete log of this run can be found in:
    npm ERR!     /home/node/.npm/_logs/2026-03-21T14_28_38_848Z-debug-0.log
    
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions