
Reproduction for Next.js CVE-2025-55182 version string confusion issue
This repository demonstrates the version string discrepancy in Next.js 16.0.7+ that causes confusion when verifying CVE-2025-55182 patch status.
After upgrading to Next.js 16.0.8, users checking their React version see 19.3.0-canary-52684925-20251110 in React DevTools, which appears to be the OLD vulnerable version. However, the actual CVE fix IS present in the react-server-dom-* packages.
Install dependencies:
npm install
Run the version check script:
npm run check-versions
Or start the dev server and check React DevTools:
npm run dev
Then open DevTools console and run:
__REACT_DEVTOOLS_GLOBAL_HOOK__.renderers.values().next()["value"]["version"]
The check-versions script will show:
react-server-dom-turbopack uses 19.3.0-canary-709fe18f-20251202 ✅ (fixed)react-server-dom-webpack uses 19.3.0-canary-709fe18f-20251202 ✅ (fixed)react-dom exports version 19.3.0-canary-52684925-20251110 ⚠️ (old string)react exports version 19.3.0-canary-52684925-20251110 ⚠️ (old string)The security fix (hasOwnProperty.call(moduleExports, metadata[2])) IS present, but the version strings are inconsistent.
Security teams and developers verifying CVE-2025-55182 remediation will see the old version string and incorrectly believe their systems are still vulnerable. This creates unnecessary confusion and potential false alarms in security audits.