AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
frontendcritical PriorityID: nextjs-15-server-action-origin-host-binding

Strict Cryptographic Origin and Host-Header Binding for Next.js 15 Server Actions

Enforces deterministic origin and host-header verification inside Next.js 15 Server Action invocations and edge proxy middleware to neutralize multitenant Host-header poisoning, cross-site action execution, and CDN edge cache pollution. Next.js 15 performs basic origin matching against the Host header, but multi-tenant deployments behind reverse proxies, CDNs, or custom domains require strict cryptographic whitelist validation against an absolute tenant authority.

Prohibited Anti-Pattern: Trusting Implicit Framework CSRF Checks on Next.js 15 Server Actions in Multi-Tenant CDN Topologies

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Strict Cryptographic Origin and Host-Header Binding for Next.js 15 Server Actions - Enforces deterministic origin and host-header verification inside Next.js 15 Server Action invocations and edge proxy middleware to neutralize multitenant Host-header poisoning, cross-site action execution, and CDN edge cache pollution. Next.js 15 performs basic origin matching against the Host header, but multi-tenant deployments behind reverse proxies, CDNs, or custom domains require strict cryptographic whitelist validation against an absolute tenant authority.
globs: src/middleware.{ts,js}, src/actions/**/*.{ts,tsx}, src/app/**/*.{ts,tsx}, src/server/**/*.{ts,tsx}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/nextjs-15-server-action-origin-host-binding"
---

# Strict Cryptographic Origin and Host-Header Binding for Next.js 15 Server Actions

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Trusting Implicit Framework CSRF Checks on Next.js 15 Server Actions in Multi-Tenant CDN Topologies

## System Constraints
You are a Principal Security Architect enforcing invariant origin-host binding across Next.js 15 Server Actions. When reviewing or authoring server-side mutations, you must mandate non-bypassable host verification, canonical origin checking, and cryptographic tenant affinity validation on all RPC boundary mutations. Reject any Server Action that relies strictly on default framework origin parsing without explicit host-to-tenant binding.

## Strict Guidelines
- Engineers MUST ALWAYS validate the incoming `Origin` and `Host`/`X-Forwarded-Host` headers against a cryptographically verified tenant registry or canonical domain whitelist prior to executing Server Action logic.
- Engineers MUST NOT rely exclusively on standard browser-level SameSite cookies or unverified Next.js automatic origin matching when deployed behind multitenant CDNs or reverse proxies capable of host-spoofing.
- Code SHOULD enforce strict timing-safe comparison or secure hashing when matching runtime incoming origins against dynamic multi-tenant custom domains stored in distributed stores.
- Services MUST throw an explicit, unhandled security error or structured rejection code (`403 Forbidden`) immediately if `headers().get('origin')` does not match the canonical host bound to the user's active session token.
- Components and Server Actions NEVER trust `window.location.host` or client-supplied hidden input fields to derive tenant context during server execution.

## Bad vs Good Implementations
### Server Action Host Poisoning Vulnerability vs. Cryptographic Tenant-Host Invariant

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Implicit reliance on the Host header allows host-header injection and tenant impersonation when deployed on reverse proxies or multi-tenant CDNs where Host headers can be spoofed or forwarded improperly.
```typescript
'use server';

import { headers } from 'next/headers';
import { db } from '@/server/db';

export async function updateTenantBilling(formData: FormData) {
  // ANTI-PATTERN: Relies on implicit Next.js 15 origin check
  // When deployed behind a wildcard CDN/proxy, malicious tenants can manipulate
  // X-Forwarded-Host or Host to bypass isolation or induce edge cache poisoning.
  const headerList = await headers();
  const host = headerList.get('host') ?? '';
  
  const tenantId = formData.get('tenantId') as string;
  const plan = formData.get('plan') as string;

  // Critical bug: tenant is directly modified without verifying if the host matches session tenant
  return await db.tenant.update({
    where: { id: tenantId },
    data: { plan }
  });
}
```

#### Production Standard (Correct)
> **Standard**: Enforces strict cryptographic timing-safe validation binding the caller's Origin and Host/X-Forwarded-Host to the immutable host recorded in the verified session token, neutralizing host-spoofing across multi-tenant domains.
```typescript
'use server';

import { headers } from 'next/headers';
import { auth } from '@/server/auth';
import { db } from '@/server/db';
import { timingSafeEqual } from 'node:crypto';

function verifyHostMatch(incomingOrigin: string, expectedHost: string): boolean {
  try {
    const originUrl = new URL(incomingOrigin);
    const expectedBuffer = Buffer.from(expectedHost.toLowerCase(), 'utf-8');
    const actualBuffer = Buffer.from(originUrl.host.toLowerCase(), 'utf-8');
    if (expectedBuffer.length !== actualBuffer.length) return false;
    return timingSafeEqual(expectedBuffer, actualBuffer);
  } catch {
    return false;
  }
}

export async function updateTenantBilling(formData: FormData) {
  const session = await auth();
  if (!session?.tenantId || !session.expectedHost) {
    throw new Error('UNAUTHORIZED_SESSION');
  }

  const headerList = await headers();
  const origin = headerList.get('origin');
  const forwardedHost = headerList.get('x-forwarded-host') ?? headerList.get('host');

  if (!origin || !forwardedHost) {
    throw new Error('MISSING_ORIGIN_OR_HOST');
  }

  // Invariant: Both the incoming origin and forwarded host must strictly
  // match the cryptographically verified tenant host bound to the session.
  const isOriginValid = verifyHostMatch(origin, session.expectedHost);
  const isHostValid = verifyHostMatch(`https://${forwardedHost}`, session.expectedHost);

  if (!isOriginValid || !isHostValid) {
    throw new Error('SECURITY_VIOLATION_ORIGIN_HOST_MISMATCH');
  }

  const plan = formData.get('plan') as string;

  return await db.tenant.update({
    where: { id: session.tenantId },
    data: { plan }
  });
}
```
Recommended MCP Servers (mcp-serverlist.com)

Equip agent with system tools to verify code for this stack.

MCP HTTP Fetch Tool
Validates live HTTP headers and origin handling behavior across configured multi-tenant reverse proxies.
Recommended Agent Skills (askills.dev)

Ready-to-use executable skill functions tailored to this stack.

Audit Server Actions Guardrail
Static AST parser identifying unbound Server Actions missing origin and host verification wrappers.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Strict Cryptographic Origin and Host-Header Binding for Next.js 15 Server Actions

Strict Cryptographic Origin and Host-Header Binding for Next.js 15 Server Actions defines an industrial-grade behavioral standard for frontend engineering. Enforces deterministic origin and host-header verification inside Next.js 15 Server Action invocations and edge proxy middleware to neutralize multitenant Host-header poisoning, cross-site action execution, and CDN edge cache pollution. Next.js 15 performs basic origin matching against the Host header, but multi-tenant deployments behind reverse proxies, CDNs, or custom domains require strict cryptographic whitelist validation against an absolute tenant authority. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: Trusting Implicit Framework CSRF Checks on Next.js 15 Server Actions in Multi-Tenant CDN Topologies Without an explicit system instruction file, developers spend hours debugging silent failures.
Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure ModeAI Symptom (The Anti-Pattern)SeverityProduction Impact & Remedy
AI Hallucination & Deprecation DriftTrusting Implicit Framework CSRF Checks on Next.js 15 Server Actions in Multi-Tenant CDN TopologiesCritical
Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production.
Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture InconsistencyAI assistants produce mixed paradigms across files, creating fragmented codebase conventions.Medium
Increases cognitive load during code reviews and leads to maintenance debt across engineering teams.
Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.
Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

1

Engineers MUST ALWAYS validate the incoming `Origin` and `Host`/`X-Forwarded-Host` headers against a cryptographically verified tenant registry or canonical domain whitelist prior to executing Server Action logic.

Engineers MUST ALWAYS validate the incoming `Origin` and `Host`/`X-Forwarded-Host` headers against a cryptographically verified tenant registry or canonical domain whitelist prior to executing Server Action logic.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
2

Engineers MUST NOT rely exclusively on standard browser-level SameSite cookies or unverified Next.js automatic origin matching when deployed behind multitenant CDNs or reverse proxies capable of host-spoofing.

Engineers MUST NOT rely exclusively on standard browser-level SameSite cookies or unverified Next.js automatic origin matching when deployed behind multitenant CDNs or reverse proxies capable of host-spoofing.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
3

Code SHOULD enforce strict timing-safe comparison or secure hashing when matching runtime incoming origins against dynamic multi-tenant custom domains stored in distributed stores.

Code SHOULD enforce strict timing-safe comparison or secure hashing when matching runtime incoming origins against dynamic multi-tenant custom domains stored in distributed stores.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
4

Services MUST throw an explicit, unhandled security error or structured rejection code (`403 Forbidden`) immediately if `headers().get('origin')` does not match the canonical host bound to the user's active session token.

Services MUST throw an explicit, unhandled security error or structured rejection code (`403 Forbidden`) immediately if `headers().get('origin')` does not match the canonical host bound to the user's active session token.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
5

Components and Server Actions NEVER trust `window.location.host` or client-supplied hidden input fields to derive tenant context during server execution.

Components and Server Actions NEVER trust `window.location.host` or client-supplied hidden input fields to derive tenant context during server execution.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
Technical Questions & Answers

Frequently Asked Technical Questions

Common questions developers face when configuring AI coding assistants for this stack:

Q:Why is Strict Cryptographic Origin and Host-Header Binding for Next.js 15 Server Actions critical for AI coding assistants?

Enforces deterministic origin and host-header verification inside Next.js 15 Server Action invocations and edge proxy middleware to neutralize multitenant Host-header poisoning, cross-site action execution, and CDN edge cache pollution. Next.js 15 performs basic origin matching against the Host header, but multi-tenant deployments behind reverse proxies, CDNs, or custom domains require strict cryptographic whitelist validation against an absolute tenant authority. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.

Q:How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (Trusting Implicit Framework CSRF Checks on Next.js 15 Server Actions in Multi-Tenant CDN Topologies) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.

Q:Which AI coding environments are supported?

This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).

Q:Can I combine this rule with other technology stacks?

Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.

Open Specification · CC BY 4.0·Free for Personal, Team & Commercial In-Repo Use

Citation & Open Source Attribution Guidelines

This specification is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). You are completely free to adapt and share this rule in your workspace. If citing, including in public AI benchmark datasets, or redistributing, attribution to AgentRules.org is required.

Related FRONTEND Rules

View all rules →
frontend
119

SolidStart 1.0 Server Functions & Async Boundaries Production Standard

SolidStart 1.0 relies on the Vinxi bundler to split `server$` closures into independent HTTP POST RPC endpoints. Direct lexical closure over client signals within `server$` scopes or failure to demarcate async boundaries with `<Suspense>` causes silent serialization failures, client-bundle secret leaks, and SSR hydration mismatches. Enforcing strict parameter passing, runtime input validation, and Solid async primitives maintains security and fine-grained reactivity across network boundaries.

frontend
119

Astro 5 Actions & Content Layer Production Standard

Enforces strict type safety and architectural correctness for Astro 5 Server Actions and the zero-waterfall Content Layer API. Prevents runtime contract mismatches, hydration mismatches, and unhandled mutation exceptions across dynamic and prerendered boundaries. Failure to follow these patterns leads to silent data fetching waterfalls, build-time cache corruptions, and unhandled server action exceptions.

frontend
51

Nuxt 4 Nitro Server Engine & Shared Directory Production Standard

Nuxt 4 enforces strict boundary segregation between client UI in the app/ directory, backend endpoints in server/, and universal contracts in shared/. Violating cross-boundary isolation or maintaining module-scoped state in Nitro server handlers causes catastrophic cross-request data corruption and hydration mismatches under concurrent production traffic. Architects must enforce request-isolated H3 event contexts, universal serialization schemas, and strict path-alias boundaries.

1 Rule in Stack

Strict