[Snyk] Fix for 1 vulnerabilities

[karencapiiro]

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

Snyk changed the following file(s):

• website/package.json
• website/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Inefficient Algorithmic Complexity SNYK-JS-MINIMATCH-15353389	170

Breaking Change Risk

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[karencapiiro]

This is a high-risk upgrade involving major versions of both ESLint and its Next.js configuration. The primary driver for this risk is ESLint's mandatory migration from the traditional .eslintrc configuration to the new eslint.config.js ("flat config") format. This is a fundamental change that requires a complete rewrite of your linting setup.

eslint v8.29.0 → v9.1.0

This is a major update with several significant breaking changes:

• New Configuration Format: ESLint v9 now defaults to eslint.config.js ("flat config"). The legacy .eslintrc format is deprecated and will be removed in ESLint v10. This requires migrating your entire configuration to the new JavaScript-based format, which involves explicitly importing plugins and configs.
• Node.js Version Requirement: Support for Node.js versions below 18.18.0 has been dropped.
• Removed Rules & Formatters: The require-jsdoc and valid-jsdoc rules have been removed, along with several core formatters like checkstyle and junit.

eslint-config-next v13.0.6 → v15.0.0

This upgrade aligns the ESLint configuration with Next.js v14/v15 and ESLint v9.

• ESLint v9 Compatibility: eslint-config-next v15 is designed to work with ESLint v9 and the new flat config system.
• Next.js v14+ Requirements: The underlying Next.js version bumps its minimum Node.js version to 18.17.
• Deprecation of next lint: Next.js is deprecating the next lint command in favor of calling the linter directly (e.g., eslint .).

Recommendation:

This upgrade cannot be merged without significant manual intervention. A full migration of the ESLint configuration is required.

1. Create eslint.config.js: Follow the official ESLint Migration Guide to convert your existing .eslintrc file to the new flat config format.
2. Update Node.js: Ensure your development and deployment environments are using Node.js v18.18.0 or newer.
3. Verify Plugin Compatibility: Check that all of your ESLint plugins have versions compatible with ESLint v9 and update them accordingly.
4. **Update

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

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​eslint-config-next@​13.0.6 ⏵ 15.0.0			-2
	npm/​eslint@​8.29.0 ⏵ 9.1.0	+6		+1	+44

View full report

[jit-ci]

🛡️ Jit Security Scan Results

🚨 Summary

• High severity ReDoS vulnerability detected in cross-spawn package

• Vulnerability introduced through eslint dependency in website/package.json

• Immediate update of cross-spawn to version 7.0.5 or later recommended

🔍 Findings

HIGH - 1 finding

1. ReDoS Vulnerability in cross-spawn Package

ID	Type	Finding	File	Severity
a7762467ad	GHSA-3xgq-45jj-v275	ReDoS Vulnerability in cross-spawn Package - A Regular Expression Denial of Service (ReDoS) vulnerability was found in cross-spawn versions before 7.0.5. This issue is introduced through the eslint dependency.	website/package.json (lines 25-25)	HIGH

🔍 AI Analysis: This is a high severity vulnerability affecting a dependency used in the project. It could potentially be exploited to cause denial of service.

Remediation:

- "eslint": "9.1.0",
+ "eslint": "^9.1.1",

▶️ Advanced Options

Help section with supported ignore actions and syntax.

Need to ignore a finding? Use commands like:

@sera ignore <finding_id> reason:accepted (reason is optional)

@sera ignore all reason:other - this is a test PR (reason is optional)

@sera ignore type:GHSA-3xgq-45jj-v275

---

^{Security scan by Jit}

[karencapiiro]

Checkmarx One – Scan Summary & Details – af458f3a-6ec2-45a7-91e4-303c97f9e143

---

New Issues (11)

Checkmarx found the following issues in this Pull Request

#	Severity	Issue	Source File / Package	Checkmarx Insight
1		CVE-2025-14874	Npm-nodemailer-6.8.0	details Recommended version: 7.0.11 Description: A flaw was found in Nodemailer versions through 7.0.10. This vulnerability allows a Denial-of-Service (DoS) via a crafted email address header that... Attack Vector: NETWORK Attack Complexity: LOW ID: Euwpbk%2BlcFvAgRu8ZA0%2BtkkwYTjb9xcH5N%2FZYz644Yk%3D Vulnerable Package
2		CVE-2025-59471	Npm-next-13.0.6	details Recommended version: 15.5.10 Description: A Denial-of-Service (DoS) vulnerability exists in self-hosted Next.js applications that have `remotePatterns` configured for the Image Optimizer. T... Attack Vector: NETWORK Attack Complexity: LOW ID: KXHCGR%2Fm2SuUB9QumcR239PAry7jMDbb7Pkn4DHiANM%3D Vulnerable Package
3		CVE-2025-66418	Python-urllib3-1.26.20	details Recommended version: 2.6.3 Description: urllib3 is a user-friendly HTTP client library for Python. Starting in version 1.24 and prior to 2.6.0, the number of links in the decompression ch... Attack Vector: NETWORK Attack Complexity: LOW ID: klPyUZPelIgqhSK4SrqqN5Aw4ypIspOW6hOLCliIxig%3D Vulnerable Package
4		CVE-2026-21441	Python-urllib3-1.26.20	details Recommended version: 2.6.3 Description: urllib3 is an HTTP client library for Python. urllib3's streaming API is designed for the efficient handling of large HTTP responses by reading the... Attack Vector: NETWORK Attack Complexity: LOW ID: L%2F3G0SrCD4ZOfSc9y36im%2BfFFSsbe%2BP%2B4JBMTI7or9M%3D Vulnerable Package
5		CVE-2026-25639	Npm-axios-1.2.1	details Recommended version: 1.13.5 Description: Axios is a promise based HTTP client for the browser and Node.js. Prior to 1.13.5, the mergeConfig function in axios crashes with a TypeError when ... Attack Vector: NETWORK Attack Complexity: LOW ID: JnBd%2BxdcC4FfoS8aZubZG5l%2FHQnNLhG2KJI%2BBdgIZaM%3D Vulnerable Package
6		Cxee52a55a-f23b	Npm-next-13.0.6	details Recommended version: 15.5.10 Description: A vulnerability affects certain React Server Components packages for versions 19.0.x, 19.1.x, and 19.2.x and frameworks that use the affected packa... Attack Vector: NETWORK Attack Complexity: LOW ID: JmmB0OaMPCSLEGnlPqpLjbFOt0zX99nO5w71a7Ge9RI%3D Vulnerable Package
7		Passwords And Secrets - Generic Secret	/docker-compose.yaml: 48	details Query to find passwords and secrets in infrastructure code. ID: XS6TYNn5u0g7jTiGz3BylPry9U8%3D
8		Memory Not Limited	/docker-compose.yaml: 4	details Memory limits should be defined for each container. This prevents potential resource exhaustion by ensuring that containers consume not more than ... ID: MzPZ0jTiyuQtT%2B81zlRApkCYJhc%3D
9		Memory Not Limited	/docker-compose.yaml: 19	details Memory limits should be defined for each container. This prevents potential resource exhaustion by ensuring that containers consume not more than ... ID: %2BbHqyR84xogGtgL5Cneja4uDtDo%3D
10		Cpus Not Limited	/docker-compose.yaml: 4	details CPU limits should be set because if the system has CPU time free, a container is guaranteed to be allocated as much CPU as it requests ID: mfmN5pFEUJC48DomKryTCnm7lkY%3D
11		Cpus Not Limited	/docker-compose.yaml: 19	details CPU limits should be set because if the system has CPU time free, a container is guaranteed to be allocated as much CPU as it requests ID: mnLPenoxG1clW%2ByxvCAvcWPZnbQ%3D

---

Fixed Issues (8)

Great job! The following issues were fixed in this Pull Request

Severity	Issue	Source File / Package
	CVE-2022-46175	Npm-json5-1.0.1
	CVE-2023-26115	Npm-word-wrap-1.2.3
	Cxdca8e59f-8bfe	Npm-inflight-1.0.6
	CVE-2025-64718	Npm-js-yaml-4.1.0
	Memory Not Limited	/docker-compose.yaml: 19
	Memory Not Limited	/docker-compose.yaml: 4
	Cpus Not Limited	/docker-compose.yaml: 19
	Cpus Not Limited	/docker-compose.yaml: 4

---

Communicate with Checkmarx by submitting a PR comment with @Checkmarx followed by one of the supported commands. Learn about the supported commands here.