Skip to content

🚨 [security] Update eslint 9.39.1 → 10.11.0 (major) - #296

Open
depfu[bot] wants to merge 1 commit into
mainfrom
depfu-update-npm-eslint-10.11.0
Open

🚨 [security] Update eslint 9.39.1 → 10.11.0 (major)#296
depfu[bot] wants to merge 1 commit into
mainfrom
depfu-update-npm-eslint-10.11.0

Conversation

@depfu

@depfu depfu Bot commented Sep 25, 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?

✳️ eslint (9.39.1 → 10.11.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 more commits than we can show here.

↗️ @​eslint/plugin-kit (indirect, 0.4.1 → 0.7.3) · Repo · Changelog

Release Notes

0.7.3 (from changelog)

Bug Fixes

  • preserve __proto__ in ConfigCommentParser results (#501) (18773d9)

0.7.2 (from changelog)

Bug Fixes

  • add missing .d.cts files while building plugin-kit (#445) (49e101b)

0.7.1 (from changelog)

Bug Fixes

  • revert re-export ESM types in CommonJS (#427) (9b16fe1)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @eslint/core bumped from ^1.2.0 to ^1.2.1

0.7.0 (from changelog)

Features

  • add languages and docs.dialects to rule meta types (#421) (7680f69)

Bug Fixes

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @eslint/core bumped from ^1.1.1 to ^1.2.0

0.6.1 (from changelog)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @eslint/core bumped from ^1.1.0 to ^1.1.1

0.6.0 (from changelog)

Features

  • add CustomRuleVisitorWithExit type to @eslint/plugin-kit (#351) (e7d1be4)
  • Add custom rule type helpers to @eslint/plugin-kit (#355) (8ac8530)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @eslint/core bumped from ^1.0.1 to ^1.1.0

0.5.1 (from changelog)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @eslint/core bumped from ^1.0.0 to ^1.0.1

0.5.0 (from changelog)

⚠ BREAKING CHANGES

  • Require Node.js ^20.19.0 || ^22.13.0 || >=24 (#297)

Features

  • Require Node.js ^20.19.0 || ^22.13.0 || >=24 (#297) (acc623c)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @eslint/core bumped from ^0.17.0 to ^1.0.0

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

↗️ acorn (indirect, 8.15.0 → 8.18.0) · Repo

Commits

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

↗️ eslint-scope (indirect, 8.4.0 → 9.1.2) · Repo · Changelog

Release Notes

9.1.2 (from changelog)

Dependencies

  • The following workspace dependencies were updated
    • devDependencies
      • espree bumped from ^11.1.1 to ^11.2.0

9.1.1 (from changelog)

Dependencies

  • The following workspace dependencies were updated
    • devDependencies
      • eslint-visitor-keys bumped from ^5.0.0 to ^5.0.1
      • espree bumped from ^11.1.0 to ^11.1.1

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

↗️ espree (indirect, 10.4.0 → 11.2.0) · Repo · Changelog

Release Notes

11.2.0 (from changelog)

Features

  • allow top level using declaration in "commonjs" (#734) (3f7fb58)

11.1.1 (from changelog)

Bug Fixes

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • eslint-visitor-keys bumped from ^5.0.0 to ^5.0.1

11.1.0 (from changelog)

Features

Bug Fixes

  • restore comments property on tokenize() return value (#721) (5603ea9)

11.0.0 (from changelog)

⚠ BREAKING CHANGES

  • Program range span entire source text (#677)
  • Require Node.js ^20.19.0 || ^22.13.0 || >=24 (#696)

Features

  • Program range span entire source text (#677) (68bbb74)
  • Require Node.js ^20.19.0 || ^22.13.0 || >=24 (#696) (9c84ecb)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • eslint-visitor-keys bumped from ^4.2.1 to ^5.0.0

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

↗️ esquery (indirect, 1.6.0 → 1.7.0) · Repo

Sorry, we couldn't find anything useful about this release.

↗️ file-entry-cache (indirect, 8.0.0 → 11.1.5) · Repo · Changelog

Release Notes

9.1.0

What's Changed

  • upgrading c8, mocha, and webpack to lastest by @jaredwray in #51
  • relative paths on current working directory by @jaredwray in #53
  • adding in additional tests on relative paths by @jaredwray in #54

Full Changelog: v9.0.0...v9.1.0

9.0.0

Breaking Changes

There are two updates that could cause potential breaking changes. The first is that we no longer support Nodejs 16 and will only be supporting Nodejs 18+.

The second is that we are now starting to support relative paths. This is the start of the process for this as the key in flat-cache still goes to an absolute path.

What's Changed

Full Changelog: v8.0.0...v9.0.0

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

↗️ flat-cache (indirect, 4.0.1 → 6.1.23) · Repo · Changelog

Release Notes

5.0.0

Breaking change is removing support for nodejs 16 and supporting 18+

What's Changed

Full Changelog: v4.0.1...v5.0.0

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

↗️ flatted (indirect, 3.3.3 → 3.4.4) · Repo

Security Advisories 🚨

🚨 Prototype Pollution via parse() in NodeJS flatted

Summary

The parse() function in flatted can use attacker-controlled string values from the parsed JSON as direct array index
keys, without validating that they are numeric. Since the internal input buffer is a JavaScript Array, accessing it
with the key "__proto__" returns Array.prototype via the inherited getter. This object is then treated as a legitimate
parsed value and assigned as a property of the output object, effectively leaking a live reference to Array.prototype
to the consumer. Any code that subsequently writes to that property will pollute the global prototype.

Root Cause

File: esm/index.js:29 (identical in cjs/index.js)

  const resolver = (input, lazy, parsed, $) => output => {
    for (let ke = keys(output), {length} = ke, y = 0; y < length; y++) {
      const k = ke[y];
      const value = output[k];    
      if (value instanceof Primitive) {
        const tmp = input[value];      // Bug is here

No validation that value is a safe numeric index input is built as a plain Array. JavaScript's property lookup on arrays traverses the prototype chain for non-numeric keys. The key "__proto__" resolves to Array.prototype, which:

  • has type "object" → passes the typeof tmp === object guard at line 30
  • is not in the parsed Set yet → passes the !parsed.has(tmp) guard.
  • The reference to Array.prototype is then enqueued in lazy and later unconditionally assigned to the output object.

Replication Steps

  const Flatted = require('flatted'); 
  const parsed = Flatted.parse('[{"x":"__proto__"}]');
  parsed.x.polluted = 'pwned';
  console.log([].polluted);  // Returns true

Impact
An attacker can supply a crafted flatted string to parse() that causes the returned object to hold a live reference to Array.prototype, enabling any downstream code that writes to that property to pollute the global prototype chain, potentially causing denial of service or code execution.

Recommended solution
Validate that the index string represents an integer within the bounds of input before accessing it:

// Before (vulnerable)
const tmp = input[value];

// After (safe)
const idx = +value; // coerce boxed String → number
const tmp = (Number.isInteger(idx) && idx >= 0 && idx < input.length)
? input[idx]
: undefined;

🚨 flatted vulnerable to unbounded recursion DoS in parse() revive phase

Summary

flatted's parse() function uses a recursive revive() phase to resolve circular references in deserialized JSON. When given a crafted payload with deeply nested or self-referential $ indices, the recursion depth is unbounded, causing a stack overflow that crashes the Node.js process.

Impact

Denial of Service (DoS). Any application that passes untrusted input to flatted.parse() can be crashed by an unauthenticated attacker with a single request.

flatted has ~87M weekly npm downloads and is used as the circular-JSON serialization layer in many caching and logging libraries.

Proof of Concept

const flatted = require('flatted');

// Build deeply nested circular reference chain

const depth = 20000;

const arr = new Array(depth + 1);

arr[0] = '{"a":"1"}';

for (let i = 1; i <= depth; i++) {

arr[i] = {"a":"<span class="pl-s1"><span class="pl-kos">${</span><span class="pl-s1">i</span> <span class="pl-c1">+</span> <span class="pl-c1">1</span><span class="pl-kos">}</span></span>"};

}

arr[depth] = '{"a":"leaf"}';


const payload = JSON.stringify(arr);

flatted.parse(payload); // RangeError: Maximum call stack size exceeded

Fix

The maintainer has already merged an iterative (non-recursive) implementation in PR #88, converting the recursive revive() to a stack-based loop.

Affected Versions

All versions prior to the PR #88 fix.

Commits

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

↗️ keyv (indirect, 4.5.4 → 5.6.0) · Repo

Sorry, we couldn't find anything useful about this release.

🆕 @​cacheable/memory (added, 2.2.0)

🆕 @​cacheable/utils (added, 2.5.0)

🆕 @​keyv/bigmap (added, 1.3.1)

🆕 @​keyv/serialize (added, 1.1.1)

🆕 @​types/esrecurse (added, 4.3.1)

🆕 cacheable (added, 2.5.0)

🆕 hashery (added, 1.5.1)

🆕 hookified (added, 1.15.1)

🆕 hookified (added, 2.2.0)

🆕 qified (added, 0.10.1)

🆕 brace-expansion (added, 5.0.12)

🆕 minimatch (added, 10.2.6)

🆕 ajv (added, 6.15.0)

🆕 eslint-visitor-keys (added, 5.0.1)

🆕 balanced-match (added, 4.0.4)

🗑️ @​eslint/eslintrc (removed)

🗑️ @​eslint/js (removed)

🗑️ globals (removed)

🗑️ json-buffer (removed)

🗑️ lodash.merge (removed)

🗑️ strip-json-comments (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)
Go to the Depfu Dashboard to see the state of your dependencies and to customize how Depfu works.

@depfu depfu Bot added dependencies Only updates dependecies depfu labels Sep 25, 2026
@depfu depfu Bot assigned Tobi2K Sep 25, 2026
@depfu depfu Bot mentioned this pull request Sep 25, 2026
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@Tobi2K Tobi2K

Labels

dependencies Only updates dependecies depfu

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@Tobi2K