Replies: 1 comment 2 replies
-
|
CVE-2025-64756 doesn't appear to be a real CVE (the numbering format suggests it might be from a scanning tool that generates pseudo-CVEs or a false positive). That said, the underlying concern is valid - Next.js v14's eslint-plugin-next does pin A few points:
If you need to override it immediately: Using npm: // package.json
{
"overrides": {
"@next/eslint-plugin-next": {
"glob": "^10.4.5"
}
}
}Using pnpm: # .pnpmfile.cjs or pnpm.overrides in package.json
pnpm:
overrides:
glob: ^10.4.5For Next.js team: If this is a legitimate vulnerability report, it would be worth bumping glob to latest 10.x in the next v14 patch release. Could you share where this CVE is documented? That would help clarify whether it's a real security issue or a scanner false positive. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
On v14 a vulnerable version (CVE-2025-64756) of
globis pinned.next.js/packages/eslint-plugin-next/package.json
Line 15 in 7b940d9
Are there any plans for an upgrade?
Additional information
No response
Example
No response
Beta Was this translation helpful? Give feedback.
All reactions