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

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

@@ -7,13 +7,14 @@
   "title": "Next.js: null origin can bypass Server Actions CSRF checks",
   "summary": "## Summary\n`origin: null` was treated as a \"missing\" origin during Server Action CSRF validation. As a result, requests from opaque contexts (such as sandboxed iframes) could bypass origin verification instead of being validated as cross-origin requests.\n\n## Impact\nAn attacker could induce a victim browser to submit Server Actions from a sandboxed context, potentially executing state-changing actions with victim credentials (CSRF).\n\n## Patches\nFixed by treating `'null'` as an explicit origin value and enforcing host/origin checks unless `'null'` is explicitly allowlisted in `experimental.serverActions.allowedOrigins`.  \n\n## Workarounds\nIf upgrade is not immediately possible:\n- Add CSRF tokens for sensitive Server Actions.\n- Prefer `SameSite=Strict` on sensitive auth cookies.\n- Do not allow `'null'` in `serverActions.allowedOrigins` unless intentionally required and additionally protected.",
   "published_at": "2026-03-17T15:30:14Z",
-  "updated_at": "2026-03-17T15:46:43.484729Z",
+  "updated_at": "2026-03-19T18:31:23.523529Z",
   "severity": "medium",
   "cvss_score": 4.0,
   "exploit_status": "unknown",
   "source_confidence": "official",
   "official_source_url": "https://github.com/vercel/next.js/security/advisories/GHSA-mq59-m269-xvcx",
   "secondary_source_urls": [
+    "https://nvd.nist.gov/vuln/detail/CVE-2026-27978",
     "https://github.com/vercel/next.js/commit/a27a11d78e748a8c7ccfd14b7759ad2b9bf097d8",
     "https://github.com/vercel/next.js",
     "https://github.com/vercel/next.js/releases/tag/v16.1.7"