Skip to content

🚨 [security] Update all of typescript-eslint 5.62.0 → 8.65.0 (major) - #7145

Open
depfu[bot] wants to merge 1 commit into
mainfrom
depfu/update/npm/group/typescript-eslint-8.65.0
Open

🚨 [security] Update all of typescript-eslint 5.62.0 → 8.65.0 (major)#7145
depfu[bot] wants to merge 1 commit into
mainfrom
depfu/update/npm/group/typescript-eslint-8.65.0

Conversation

@depfu

@depfu depfu Bot commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ @​typescript-eslint/eslint-plugin (5.62.0 → 8.65.0) · Repo · Changelog

Release Notes

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by 22 commits:

✳️ @​typescript-eslint/parser (5.62.0 → 8.65.0) · Repo · Changelog

Release Notes

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by 22 commits:

✳️ debug (4.4.1 → 4.4.3) · Repo · Changelog

Security Advisories 🚨

🚨 debug@4.4.2 contains malware after npm account takeover

Impact

On 8 September 2025, the npm publishing account for debug was taken over after a phishing attack. Version 4.4.2 was published, functionally identical to the previous patch version, but with a malware payload added attempting to redirect cryptocurrency transactions to the attacker's own addresses from within browser environments.

Local environments, server environments, command line applications, etc. are not affected. If the package was used in a browser context (e.g. a direct <script> inclusion, or via a bundling tool such as Babel, Rollup, Vite, Next.js, etc.) there is a chance the malware still exists and such bundles will need to be rebuilt.

The malware seemingly only targets cryptocurrency transactions and wallets such as MetaMask. See references below for more information on the payload.

Patches

npm removed the offending package from the registry over the course of the day on 8 September, preventing further downloads from npm proper.

On 13 September, the package owner published new patch versions to help cache-bust those using private registries who might still have the compromised version cached. This version is functionally identical to the previously known-good version, published as a patch version bump above the compromised version.

Users should upgrade to the latest patch version, completely remove their node_modules directory, clean their package manager's global cache, and rebuild any browser bundles from scratch.

Those operating private registries or registry mirrors should purge the offending versions from any caches.

References

Point of Contact

In the event suspicious behavior is still observed for the package listed in this security advisory after performing all of the above cleaning operations (see Patches above), please reach out via one of the following channels of communication:

Release Notes

4.4.3

Functionally identical release to 4.4.1.

Version 4.4.2 is compromised. Please see #1005.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 1 commit:

↗️ @​typescript-eslint/type-utils (indirect, 5.62.0 → 8.65.0) · Repo · Changelog

Release Notes

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by 22 commits:

↗️ picomatch (indirect, 4.0.3 → 4.0.5) · Repo · Changelog

Security Advisories 🚨

🚨 Picomatch has a ReDoS vulnerability via extglob quantifiers

Impact

picomatch is vulnerable to Regular Expression Denial of Service (ReDoS) when processing crafted extglob patterns. Certain patterns using extglob quantifiers such as +() and *(), especially when combined with overlapping alternatives or nested extglobs, are compiled into regular expressions that can exhibit catastrophic backtracking on non-matching input.

Examples of problematic patterns include +(a|aa), +(*|?), +(+(a)), *(+(a)), and +(+(+(a))). In local reproduction, these patterns caused multi-second event-loop blocking with relatively short inputs. For example, +(a|aa) compiled to ^(?:(?=.)(?:a|aa)+)$ and took about 2 seconds to reject a 41-character non-matching input, while nested patterns such as +(+(a)) and *(+(a)) took around 29 seconds to reject a 33-character input on a modern M1 MacBook.

Applications are impacted when they allow untrusted users to supply glob patterns that are passed to picomatch for compilation or matching. In those cases, an attacker can cause excessive CPU consumption and block the Node.js event loop, resulting in a denial of service. Applications that only use trusted, developer-controlled glob patterns are much less likely to be exposed in a security-relevant way.

Patches

This issue is fixed in picomatch 4.0.4, 3.0.2 and 2.3.2.

Users should upgrade to one of these versions or later, depending on their supported release line.

Workarounds

If upgrading is not immediately possible, avoid passing untrusted glob patterns to picomatch.

Possible mitigations include:

  • disable extglob support for untrusted patterns by using noextglob: true
  • reject or sanitize patterns containing nested extglobs or extglob quantifiers such as +() and *()
  • enforce strict allowlists for accepted pattern syntax
  • run matching in an isolated worker or separate process with time and resource limits
  • apply application-level request throttling and input validation for any endpoint that accepts glob patterns

Resources

🚨 Picomatch: Method Injection in POSIX Character Classes causes incorrect Glob Matching

Impact

picomatch is vulnerable to a method injection vulnerability (CWE-1321) affecting the POSIX_REGEX_SOURCE object. Because the object inherits from Object.prototype, specially crafted POSIX bracket expressions (e.g., [[:constructor:]]) can reference inherited method names. These methods are implicitly converted to strings and injected into the generated regular expression.

This leads to incorrect glob matching behavior (integrity impact), where patterns may match unintended filenames. The issue does not enable remote code execution, but it can cause security-relevant logic errors in applications that rely on glob matching for filtering, validation, or access control.

All users of affected picomatch versions that process untrusted or user-controlled glob patterns are potentially impacted.

Patches

This issue is fixed in picomatch 4.0.4, 3.0.2 and 2.3.2.

Users should upgrade to one of these versions or later, depending on their supported release line.

Workarounds

If upgrading is not immediately possible, avoid passing untrusted glob patterns to picomatch.

Possible mitigations include:

  • Sanitizing or rejecting untrusted glob patterns, especially those containing POSIX character classes like [[:...:]].

  • Avoiding the use of POSIX bracket expressions if user input is involved.

  • Manually patching the library by modifying POSIX_REGEX_SOURCE to use a null prototype:

    const POSIX_REGEX_SOURCE = {
  __proto__: null,
  alnum: 'a-zA-Z0-9',
  alpha: 'a-zA-Z',
  // ... rest unchanged
};

Resources

Release Notes

4.0.5

What's Changed

  • fix: preserve all branches when rewriting risky repeated extglobs by @MerlijnW70 in #182
  • fix: honor the windows option when matching basenames by @MerlijnW70 in #183

New Contributors

Full Changelog: 4.0.4...4.0.5

4.0.4

This is a security release fixing several security relevant issues.

What's Changed

Full Changelog: 4.0.3...4.0.4

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 30 commits:

🆕 @​typescript-eslint/project-service (added, 8.65.0)

🆕 @​typescript-eslint/tsconfig-utils (added, 8.65.0)

🆕 fdir (added, 6.5.0)

🆕 tinyglobby (added, 0.2.17)

🆕 brace-expansion (added, 5.0.8)

🆕 minimatch (added, 10.2.5)

🆕 eslint-visitor-keys (added, 5.0.1)

🆕 semver (added, 7.8.5)

🆕 @​typescript-eslint/scope-manager (added, 8.65.0)

🆕 @​typescript-eslint/types (added, 8.65.0)

🆕 @​typescript-eslint/typescript-estree (added, 8.65.0)

🆕 @​typescript-eslint/utils (added, 8.65.0)

🆕 @​typescript-eslint/visitor-keys (added, 8.65.0)

🆕 balanced-match (added, 4.0.4)

🆕 ignore (added, 7.0.6)

🆕 ts-api-utils (added, 2.5.0)

🗑️ archiver (removed)

🗑️ archiver-utils (removed)

🗑️ archiver-utils (removed)

🗑️ compress-commons (removed)

🗑️ crc-32 (removed)

🗑️ crc32-stream (removed)

🗑️ electron-builder-squirrel-windows (removed)

🗑️ lazystream (removed)

🗑️ lodash.defaults (removed)

🗑️ lodash.difference (removed)

🗑️ lodash.flatten (removed)

🗑️ lodash.isplainobject (removed)

🗑️ lodash.union (removed)

🗑️ natural-compare-lite (removed)

🗑️ react-native-url-polyfill (removed)

🗑️ readdir-glob (removed)

🗑️ webidl-conversions (removed)

🗑️ whatwg-url-without-unicode (removed)

🗑️ zip-stream (removed)

Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu Bot added depfu no-changelog no-jira-ticket Skip checking the PR title for Jira reference labels Jul 27, 2026
@depfu
depfu Bot requested a review from a team July 27, 2026 18:10
@cla-bot cla-bot Bot added the cla: yes label Jul 27, 2026
@depfu depfu Bot mentioned this pull request Jul 27, 2026
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

cla: yes depfu no-changelog no-jira-ticket Skip checking the PR title for Jira reference

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants