Skip to content

[Snyk] Fix for 1 vulnerabilities#3667

Open
cc-prodsec wants to merge 1 commit intorelease-2.9.xfrom
snyk-fix-ec37d3f60ef4f091624bbdfab147f340
Open

[Snyk] Fix for 1 vulnerabilities#3667
cc-prodsec wants to merge 1 commit intorelease-2.9.xfrom
snyk-fix-ec37d3f60ef4f091624bbdfab147f340

Conversation

@cc-prodsec
Copy link
Collaborator

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

  • packages/internal-lib-build/package.json
  • packages/internal-lib-build/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-AJV-15274295
  803  

Breaking Change Risk

Merge Risk: High

Notice: This assessment is enhanced by AI.


Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Regular Expression Denial of Service (ReDoS)

…-build/package-lock.json to reduce vulnerabilities

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-AJV-15274295
@cc-prodsec cc-prodsec requested a review from a team as a code owner February 14, 2026 11:57
@cc-prodsec
Copy link
Collaborator Author

Merge Risk: High

This upgrade includes major versions for both eslint and babel-loader, introducing significant breaking changes that require developer action.

eslint@7.32.0 → eslint@10.0.0

Risk: HIGH

This upgrade spans three major versions (v8, v9, and v10) and introduces substantial breaking changes. The most critical change is the complete removal of the traditional .eslintrc configuration in favor of the new "flat config" format (eslint.config.js).

Key Breaking Changes:

  • Configuration Rewrite: You must migrate your .eslintrc configuration file to the new eslint.config.js format. The old format is no longer supported in v10.
  • Node.js Version: Support for older Node.js versions has been dropped. ESLint v10 requires Node.js ^20.19.0 or newer.
  • Rule and Formatter Removals: Several core rules (e.g., valid-jsdoc) and formatters have been removed.
  • API Changes: The CLIEngine class was removed in v8, and function-style rules are no longer supported as of v9.

Recommendation: This is a significant migration. It is highly recommended to follow the official ESLint migration guides for v8, v9, and v10 to update your configuration and rules.

babel-loader@8.3.0 → babel-loader@10.0.0

Risk: MEDIUM

This upgrade also crosses major versions (v9 and v10).

Key Breaking Changes:

  • Environment Support:
    • Node.js: babel-loader v10 requires Node.js ^18.20.0, ^20.10.0, or >=22.0.0.
    • webpack: Requires webpack >= 5.61.0. Support for webpack 4 was likely dropped in v9.

Recommendation: Verify that your Node.js and webpack versions meet the new requirements. If you are using webpack 4, you will need to upgrade your webpack version as part of this change.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

@cc-prodsec
Copy link
Collaborator Author

cc-prodsec commented Feb 14, 2026

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

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.

2 participants