Skip to content

chore: update dependency minimatch to v11 [security] - #2616

Draft
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/npm-minimatch-vulnerability
Draft

renovate[bot] wants to merge 1 commit into
masterfrom
renovate/npm-minimatch-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Nov 1, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
minimatch ^10.2.6 → ^11.0.0 age adoption passing confidence

minimatch has potential denial of service via globparts amplification

CVE-2026-118764 / GHSA-g3hv-75wg-m249

More information

Details

minimatch 10.2.6 contains an attacker-controlled pattern amplification in firstPhasePreProcess() when optimizationLevel >= 2.

researcher: Reid Downing (b1nv0id)
files:

  • src/index.ts: 690-770
  • src/index.ts: 780-796

issue:
input-controlled growth of globParts during first-phase preprocessing, followed by quadratic second-phase processing.

the **/../ transformation clones a globparts entry and appends the clone to the same globparts array:

parts.splice(gs, 1)
const other = parts.slice(0)
other[gs] = '**'
globParts.push(other)

this occurs inside a do...while (didSomething) fixpoint loop, allowing generated entries to be processed again.

the expanded globparts array is subsequently processed by secondPhasePreProcess(), which performs pairwise comparisons:

for (let i = 0; i < globParts.length - 1; i++) {
  for (let j = i + 1; j < globParts.length; j++) {
    this.partsMatch(...)
  }
}

an attacker who can supply a glob pattern can therefore cause additional pattern entries to be generated during preprocessing, followed by quadratic pairwise processing, resulting in excessive cpu and memory consumption.

Severity

  • CVSS Score: 6.9 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

isaacs/minimatch (minimatch)

v11.0.1

Compare Source

v11.0.0

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot requested a review from a team November 1, 2026 14:30
@renovate renovate Bot changed the title chore: update dependency minimatch to v11 [security] chore: update dependency minimatch to v11 [security] - autoclosed Nov 4, 2026
@renovate renovate Bot closed this Nov 4, 2026
@renovate
renovate Bot deleted the renovate/npm-minimatch-vulnerability branch November 4, 2026 19:08
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate Bot changed the title chore: update dependency minimatch to v11 [security] - autoclosed chore: update dependency minimatch to v11 [security] Nov 9, 2026
@renovate renovate Bot reopened this Nov 9, 2026
@renovate
renovate Bot force-pushed the renovate/npm-minimatch-vulnerability branch 2 times, most recently from 4097b7b to 6638a2a Compare November 9, 2026 05:50
@renovate

renovate Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants