SecOps SignalSecurity Intelligence Workspace
Loading collection status
Vulnerabilities/CVE-2026-64645Public Intelligence Dossier
Source: vercel · Limited verification•Last verified: •Collection Degraded
CVE-2026-64645Unknown / EvaluatingHIGH (raw)CVSS 8.3CWE-601

Next.js is a React framework for building full-stack web applications

Published: 27 Jul 2026•Last updated: 24 Oct 2026, 06:40 PM IST•Source identifier: security-advisories@github.com
Dossier completeness: source-provided sections 2 / 3 · rule guidance available. Missing source facts count as incomplete.
Official source
CISA KEV catalog
Unknown
KEV status was not determined.
CVSS score
8.3HIGH (raw)
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Metric sourcesecurity-advisories@github.com
EPSS probability
0.4%0.004
Percentile36th
Weakness type
CWE-601
CWE-918
Remediation
Patch status unknown
No fixed version or KB recorded

Why It Matters

Analysis dossier

Why It Matters

Next.js is a React framework for building full-stack web applications. In versions 12.0.0 through 15.5.20 and 16.0.0 through 16.2.10, a rewrites() or redirects() rule that builds its external destination hostname from request-controlled input can be pointed at an arbitrary hostname, regardless of the rule's hostname suffix. For a rewrite, Next.js proxies the request to that arbitrary host and serves the response from the application's origin, leading to Server-Side Request forgery. A redirects() rule configured this way is vulnerable to an Open Redirect. This issue has been fixed in versions 15.5.21 and 16.2.11.

SOC priority

High

Actively exploited (source statement)

Unknown

Publicly disclosed

Unknown

Risk basis: SOC ecosystem technology relevance; HIGH severity; Source severity; no confirmed exploitation signal

Affected Products & Remediation

1 source-backed product
Affected products and versions (source)
  • vercel next.js · >= 12.0.0 < 15.5.21; >= 16.0.0 < 16.2.11 · NVD CPE · Source
Recorded patch / KBNot provided by source

Vendor or catalog guidance (source)

Not provided by source

Known exploitation (source facts)

Only what a source states. Unknown means no source has said either way; it is not "not exploited".

CISA KEV
Unknown
Exploited (source statement)
Unknown
Publicly disclosed (source)
Unknown

Suggested hunting (rule-based inference)

SecOps Signal recommendation (rule-based inference). These steps are hunting hypotheses from the vulnerability class; they do not state or imply that exploitation occurred here or anywhere.

Matched ssrf (CWE-918); network-unauthenticated (CVSS AV:N, CVSS PR:N, CVSS UI:N)

Exposure

  1. Identify affected server-side request features and deployed versions.Telemetry: Application inventory · The specific feature must be confirmed from the advisory. · Rule ssrf
  2. Identify devices reporting this CVE and note which expose the affected service to untrusted networks.Telemetry: DeviceTvmSoftwareVulnerabilities · A network-reachable, no-privilege vector makes internet-facing instances the first exposure question. · Rule network-unauthenticated

Exploitation evidence

  1. Review unusual outbound connections from the affected service to internal or metadata endpoints.Telemetry: DeviceNetworkEvents · Outbound patterns can support SSRF hunting. · Rule ssrf
Show more (2)

Exploitation evidence

  1. Review inbound connections to the affected service from unexpected sources since the advisory date.Telemetry: DeviceNetworkEvents · Hunting hypothesis from the CVSS vector; it does not show that exploitation occurred. · Rule network-unauthenticated

Response

  1. Verify the vendor fix and confirm expected egress after deployment.Telemetry: DeviceNetworkEvents · Post-change telemetry helps validate mitigation. · Rule ssrf

CISA KEV Record

CISA KEV status was not determined for this record.

Change History & Source Data

— No recorded material change

CNA / source
security-advisories@github.com
Record status · verification
UPDATED · NVD API
CPE
cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:*

Evidence & Provenance

3 public sources
github.comSource recordnvd.nist.govSource recordgithub.comSource record

Linked by the query's stored exact CVE association. Review required tables and validation status before use.

Detection Hunting Query
Target: DeviceTvmSoftwareVulnerabilities•Defender XDR
Detect endpoints exposed to CVE-2026-64645
Purpose: Exposure assessment (Category: Exposure Check)Why linked: Query metadata names CVE-2026-64645
DeviceTvmSoftwareVulnerabilities| where CveId == "CVE-2026-64645"| project DeviceId, DeviceName, OSPlatform, OSVersion, SoftwareVendor, SoftwareName, SoftwareVersion, CveId, VulnerabilitySeverityLevel, RecommendedSecurityUpdate, RecommendedSecurityUpdateId| sort by VulnerabilitySeverityLevel desc
Schema Checked · Not runtime validatedSource: SecOps Signal deterministic template · Limited verificationStatic screening: Passed structure and schema checks; tenant execution is not verified.
Open KQL Library

Looking up related community queries…

Loading related intelligence

Correlated briefings

SecOps Signal surfaces public advisory facts only. A missing value means the source has not published it, not that your environment is unaffected. No tenant inventory is connected.