fix(deps): upgrade React and Next.js for security vulnerabilities

[lyzno1]

Upgrade to patched versions to address:

• CVE-2025-55184: Denial of Service (High, CVSS 7.5)
• CVE-2025-67779: Additional DoS case (High, CVSS 7.5)
• CVE-2025-55183: Source Code Exposure (Medium, CVSS 5.3)

Package updates:

• react: 19.1.1 → 19.1.4
• react-dom: 19.1.1 → 19.1.4
• next: 15.4.7 → 15.4.10

Previous patches (19.0.2, 19.1.3, 19.2.2) were incomplete.
These new versions provide complete mitigation.

References:

• react.dev/blog/2025/12/11/denial-of-service-and-source-code
• nextjs.org/blog/security-update-2025-12-11

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
agentif-ui	Ready	Preview	Comment	Dec 12, 2025 5:29am

[gemini-code-assist]

Summary of Changes

Hello @lyzno1, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request is a crucial security update, upgrading key frontend dependencies to address recently discovered vulnerabilities. The changes ensure the application is protected against potential Denial of Service attacks and source code exposure, enhancing the overall stability and security posture of the project.

Highlights

• Security Vulnerability Mitigation: This pull request addresses critical security vulnerabilities, including Denial of Service (CVE-2025-55184, CVE-2025-67779) and Source Code Exposure (CVE-2025-55183), by upgrading core dependencies to patched versions.
• Dependency Upgrades: The react and react-dom packages have been upgraded from version 19.1.1 to 19.1.4. The next package has been updated from 15.4.7 to 15.4.10.
• Complete Mitigation: The updated versions provide a complete mitigation for the identified vulnerabilities, as previous patches were noted to be incomplete.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request correctly upgrades react, react-dom, and next to their patched versions to address the mentioned security vulnerabilities. The changes in package.json and the corresponding updates in pnpm-lock.yaml are appropriate and look good. As a follow-up, I'd suggest also updating the eslint-config-next dev dependency to 15.4.10 to match the new next version. This would ensure your linting rules are aligned with the framework version, preventing potential inconsistencies. Since this was outside the diff, I'm mentioning it here for your consideration.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Align Next SWC binaries with 15.4.10 upgrade

next is bumped to 15.4.10, but the lock still pins all optional @next/swc-* binaries to 15.4.8. Next releases expect their compiler binaries at the same patch level; leaving the lock at 15.4.8 means installs will fetch the older compiler, so the intended security fix in the 15.4.10 toolchain is never applied and the runtime can load a mismatched SWC binary. Please regenerate the lock so the @next/swc-* entries match 15.4.10.

Useful? React with 👍 / 👎.