更新: 114 个文件 - 2026-03-19 16:45:07

08-threat-intel/registry/advisories/nextjs--CVE-2026-27977.json

@@ -7,13 +7,14 @@
   "title": "Next.js: null origin can bypass dev HMR websocket CSRF checks",
   "summary": "## Summary\nIn `next dev`, cross-site protection for internal websocket endpoints could treat `Origin: null` as a bypass case even if [`allowedDevOrigins`](https://nextjs.org/docs/app/api-reference/config/next-config-js/allowedDevOrigins) is configured, allowing privacy-sensitive/opaque contexts (for example sandboxed documents) to connect unexpectedly.\n\n## Impact\nIf a dev server is reachable from attacker-controlled content, an attacker may be able to connect to the HMR websocket channel and interact with dev websocket traffic. This affects development mode only.\nApps without a configured [`allowedDevOrigins`](https://nextjs.org/docs/app/api-reference/config/next-config-js/allowedDevOrigins) still allow connections from any origin.\n\n## Patches\nFixed by validating `Origin: null` through the same cross-site origin-allowance checks used for other origins.  \n\n## Workarounds\nIf upgrade is not immediately possible:\n- Do not expose `next dev` to untrusted networks.\n- Block websocket upgrades to `/_next/webpack-hmr` when `Origin` is `null` at your proxy.",
   "published_at": "2026-03-17T15:29:48Z",
-  "updated_at": "2026-03-17T15:46:26.028580Z",
+  "updated_at": "2026-03-19T18:32:38.608475Z",
   "severity": "medium",
   "cvss_score": 4.0,
   "exploit_status": "unknown",
   "source_confidence": "official",
   "official_source_url": "https://github.com/vercel/next.js/security/advisories/GHSA-jcc7-9wpm-mj36",
   "secondary_source_urls": [
+    "https://nvd.nist.gov/vuln/detail/CVE-2026-27977",
     "https://github.com/vercel/next.js/commit/862f9b9bb41d235e0d8cf44aa811e7fd118cee2a",
     "https://github.com/vercel/next.js",
     "https://github.com/vercel/next.js/releases/tag/v16.1.7"