[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
	Regular Expression Denial of Service (ReDoS) SNYK-JS-MINIMATCH-15309438	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:

🦉 Regular Expression Denial of Service (ReDoS)

[karencapiiro]

This upgrade to ESLint v10 and eslint-config-next v15 introduces significant and mandatory breaking changes. The primary impact is the complete removal of the legacy .eslintrc configuration system in favor of the new eslint.config.js (flat config) format. This requires a full migration of your linting configuration.

Key Breaking Changes:

• ESLint Configuration Migration (Mandatory):

  • ESLint v9 made the new "flat config" (eslint.config.js) the default and deprecated the old .eslintrc format.
  • ESLint v10 completely removes support for .eslintrc files. The ESLINT_USE_FLAT_CONFIG escape hatch is no longer available. All related CLI flags have also been removed.
  • You must rewrite your entire configuration into the new eslint.config.js format. This includes how plugins and parsers are imported and configured.

• Node.js Version Requirement:

  • ESLint v9 requires Node.js v18.18.0 or higher.
  • ESLint v10 increases this requirement to Node.js v20.19.0 or higher.

• eslint-config-next Compatibility:

  • Next.js v15 adds support for ESLint v9.
  • However, eslint-config-next has known compatibility issues with the new flat config system, which may require using a compatibility utility (@eslint/eslintrc) to bridge the gap.

Recommendation: This is a high-effort migration that cannot be completed by simply updating package versions. A dedicated effort is required to rewrite the ESLint configuration from .eslintrc.js to eslint.config.js. It is highly recommended to follow the official ESLint migration guides to perform this update.

• Source: ESLint v9 Migration Guide, ESLint v10 Release Notes

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
	pypi/​starlette@​0.22.0
	npm/​eslint@​8.29.0 ⏵ 10.0.0	-1		+1	+45
	pypi/​uvicorn@​0.20.0
	pypi/​typer@​0.7.0
	pypi/​sqlmodel@​0.0.8

View full report

[jit-ci]

🛡️ Jit Security Scan Results

🚨 Summary

• High severity ReDoS vulnerability detected in ajv dependency

• Vulnerability affects eslint package used in the project

• Immediate update of dependencies recommended to mitigate security risk

🔍 Findings

HIGH - 1 finding

1. ReDoS Vulnerability in ajv Dependency

ID	Type	Finding	File	Severity
bd7319f5c6	GHSA-2g4f-4pwh-qvx6	ReDoS Vulnerability in ajv Dependency - A high severity Regular Expression Denial of Service (ReDoS) vulnerability has been detected in the ajv library, affecting versions through 8.17.1. This vulnerability is introduced via the eslint dependency.	website/package.json (lines 25-25)	HIGH

🔍 AI Analysis: This is a high severity vulnerability in a dependency that could lead to denial of service attacks. It affects a core development tool (eslint) which is likely used across the project.

Remediation:

- "eslint": "10.0.0",
+ "eslint": "^8.0.0",

▶️ 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-2g4f-4pwh-qvx6

---

^{Security scan by Jit}

[karencapiiro]

Checkmarx One – Scan Summary & Details – 15ba16d8-919b-4d17-a1cc-deeff063c910

---

New Issues (12)

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: AaVgCgY%2FH%2FoVRVLlaxkLMb0uoIfyUUzLfFQpxHPqmec%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-2025-69873	Npm-ajv-6.12.6	details Recommended version: 8.18.0 Description: ajv (Another JSON Schema Validator) through version 8.17.1 is vulnerable to Regular Expression Denial of Service (ReDoS) when the "$data" option is... Attack Vector: NETWORK Attack Complexity: LOW ID: 8En2%2FacX5rTYl0xSWtwEEi8iCHu%2FiU8QFCZs3i5J5Rw%3D Vulnerable Package
5		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
6		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
7		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
8		Passwords And Secrets - Generic Secret	/docker-compose.yaml: 48	details Query to find passwords and secrets in infrastructure code. ID: XS6TYNn5u0g7jTiGz3BylPry9U8%3D
9		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
10		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
11		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
12		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 (10)

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
	CVE-2024-21538	Npm-cross-spawn-7.0.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
	CVE-2025-5889	Npm-brace-expansion-1.1.11
	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.