Advisories
For your digest

minimatch: minimatch has a ReDoS via repeated wildcards with non-matching literal in pattern

It touches something Phylax follows. No evidence of use yet.

Does it affect what I run?

minimatch (npm)

Checked in your browser. The version you type is not sent anywhere.

Who is affected

  • minimatch (npm): from 10.0.0, before 10.2.1
  • minimatch (npm): from 9.0.0, before 9.0.6
  • minimatch (npm): from 8.0.0, before 8.0.5
  • minimatch (npm): from 7.0.0, before 7.4.7
  • minimatch (npm): from 6.0.0, before 6.2.1
  • minimatch (npm): from 5.0.0, before 5.1.7
  • minimatch (npm): from 4.0.0, before 4.2.4
  • minimatch (npm): every version, before 3.1.3

The fix

  • minimatch (npm) fixed in 10.2.1

    npm
    npm install minimatch@10.2.1
    pnpm
    pnpm add minimatch@10.2.1
    yarn
    yarn add minimatch@10.2.1
    bun
    bun add minimatch@10.2.1
    Check what is installed
    npm ls minimatch
    Paste into Cursor, Lovable or Claude Code
    Upgrade the npm dependency minimatch to 10.2.1 or the nearest later release, to fix CVE-2026-26996. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • minimatch (npm) fixed in 9.0.6

    npm
    npm install minimatch@9.0.6
    pnpm
    pnpm add minimatch@9.0.6
    yarn
    yarn add minimatch@9.0.6
    bun
    bun add minimatch@9.0.6
    Check what is installed
    npm ls minimatch
    Paste into Cursor, Lovable or Claude Code
    Upgrade the npm dependency minimatch to 9.0.6 or the nearest later release, to fix CVE-2026-26996. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • minimatch (npm) fixed in 8.0.5

    npm
    npm install minimatch@8.0.5
    pnpm
    pnpm add minimatch@8.0.5
    yarn
    yarn add minimatch@8.0.5
    bun
    bun add minimatch@8.0.5
    Check what is installed
    npm ls minimatch
    Paste into Cursor, Lovable or Claude Code
    Upgrade the npm dependency minimatch to 8.0.5 or the nearest later release, to fix CVE-2026-26996. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • minimatch (npm) fixed in 7.4.7

    npm
    npm install minimatch@7.4.7
    pnpm
    pnpm add minimatch@7.4.7
    yarn
    yarn add minimatch@7.4.7
    bun
    bun add minimatch@7.4.7
    Check what is installed
    npm ls minimatch
    Paste into Cursor, Lovable or Claude Code
    Upgrade the npm dependency minimatch to 7.4.7 or the nearest later release, to fix CVE-2026-26996. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • minimatch (npm) fixed in 6.2.1

    npm
    npm install minimatch@6.2.1
    pnpm
    pnpm add minimatch@6.2.1
    yarn
    yarn add minimatch@6.2.1
    bun
    bun add minimatch@6.2.1
    Check what is installed
    npm ls minimatch
    Paste into Cursor, Lovable or Claude Code
    Upgrade the npm dependency minimatch to 6.2.1 or the nearest later release, to fix CVE-2026-26996. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • minimatch (npm) fixed in 5.1.7

    npm
    npm install minimatch@5.1.7
    pnpm
    pnpm add minimatch@5.1.7
    yarn
    yarn add minimatch@5.1.7
    bun
    bun add minimatch@5.1.7
    Check what is installed
    npm ls minimatch
    Paste into Cursor, Lovable or Claude Code
    Upgrade the npm dependency minimatch to 5.1.7 or the nearest later release, to fix CVE-2026-26996. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • minimatch (npm) fixed in 4.2.4

    npm
    npm install minimatch@4.2.4
    pnpm
    pnpm add minimatch@4.2.4
    yarn
    yarn add minimatch@4.2.4
    bun
    bun add minimatch@4.2.4
    Check what is installed
    npm ls minimatch
    Paste into Cursor, Lovable or Claude Code
    Upgrade the npm dependency minimatch to 4.2.4 or the nearest later release, to fix CVE-2026-26996. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • minimatch (npm) fixed in 3.1.3

    npm
    npm install minimatch@3.1.3
    pnpm
    pnpm add minimatch@3.1.3
    yarn
    yarn add minimatch@3.1.3
    bun
    bun add minimatch@3.1.3
    Check what is installed
    npm ls minimatch
    Paste into Cursor, Lovable or Claude Code
    Upgrade the npm dependency minimatch to 3.1.3 or the nearest later release, to fix CVE-2026-26996. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.

Fix commands generated from the advisory's versions. No model wrote them.

In plain words

Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.

Evidence

No evidence that it is being used, or can be. It is listed because of what it affects.

Timeline

  1. First published here, as "For your digest".