Fix cve-2025-55182 vulnerability #891
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update Next.js and React packages to patched versions and regenerate lockfile to fix CVE-2025-55182.
This update addresses the vulnerability by upgrading the framework/tooling stack to releases that no longer include the vulnerable React 19 builds, as advised by Vercel.
Note
Upgrades Next.js and React to patched releases and updates typing/usages to be compatible, addressing the reported vulnerability.
react/react-domto19.2.1andnextto15.4.8(plus related@next/*,@types/react*, and ecosystem packages) to use patched builds.src/app/providers.tsx: adjustuseReftoT | undefinedinusePrevious.src/components/ArticleContent.tsx: add explicit type guards forReact.isValidElement, handle nullable children, and simplifycloneElementusage.src/components/DevToolCard.tsx: switch toFCand changerenderToolDetailsto returnReactElement.Written by Cursor Bugbot for commit 84b574b. This will update automatically on new commits. Configure here.