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

Next.js 15 Server Action Ephemeral Cryptographic Nonce-Binding Standard

Next.js 15 Server Actions must enforce cryptographic nonce-binding to neutralize distributed replay attacks and session-riding state transitions. Every mutation-bearing Server Action must validate an ephemeral, HMAC-signed execution nonce strictly coupled to the authenticated user's session identifier, timestamp bounds, and mutation signature. State-changing operations must reject unverified payloads, guarantee single-use consumption, and strictly enforce atomic invalidation.

Prohibited Anti-Pattern: Executing Naked State Mutations in Next.js Server Actions Without Ephemeral Cryptographic Nonce Verification

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Next.js 15 Server Action Ephemeral Cryptographic Nonce-Binding Standard - Next.js 15 Server Actions must enforce cryptographic nonce-binding to neutralize distributed replay attacks and session-riding state transitions. Every mutation-bearing Server Action must validate an ephemeral, HMAC-signed execution nonce strictly coupled to the authenticated user's session identifier, timestamp bounds, and mutation signature. State-changing operations must reject unverified payloads, guarantee single-use consumption, and strictly enforce atomic invalidation.
globs: src/actions/**/*.{ts,tsx}, src/app/**/*.{ts,tsx}, src/lib/security/**/*.{ts,tsx}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/nextjs-15-server-action-nonce-binding"
---

# Next.js 15 Server Action Ephemeral Cryptographic Nonce-Binding Standard

> **Severity**: CRITICAL | **Category**: security
> **Anti-Pattern Warning**: Executing Naked State Mutations in Next.js Server Actions Without Ephemeral Cryptographic Nonce Verification

## System Constraints
You are a Principal Security Architect enforcing the Next.js 15 Server Action Cryptographic Nonce-Binding Standard. Reject any Server Action implementation that mutates persistent state without validating a cryptographically bound, single-use, time-delimited nonce attached to the active session. Ensure nonces contain authenticated session context, enforce strict temporal drift thresholds, and leverage constant-time verification.

## Strict Guidelines
- Engineers MUST ALWAYS verify a cryptographically signed execution nonce before executing state-changing business logic in Server Actions.
- Engineers MUST NOT trust Next.js Host/Origin headers alone to guard critical financial, authorization, or destructive mutations against replay attacks.
- Code MUST bind the session identity (e.g., userId or sessionId) directly into the signed nonce payload to prevent cross-session token migration.
- Services MUST implement constant-time comparison (e.g., crypto.timingSafeEqual) when validating HMAC signatures on action tokens.
- Components NEVER render form actions or invoke mutations without injecting an ephemeral nonce issued by an authoritative server component or session token provider.

## Bad vs Good Implementations
### Naked Server Action Mutation vs Cryptographically Bound Nonce Invariant

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: The action relies solely on ambient cookie authentication without verifying intentionality or single-use execution tokens. An interceptor, rogue client script, or repeated network request can replay this action payload indefinitely within an active session.
```typescript
'use server';

import { auth } from '@/lib/auth';
import { db } from '@/lib/db';
import { revalidatePath } from 'next/cache';

interface TransferFundsInput {
  recipientId: string;
  amountInCents: number;
}

// ANTI-PATTERN: Naked Server Action accepting direct inputs.
// Vulnerable to replay attacks, race-condition double spending,
// and malicious repeated invocation via captured network payloads.
export async function transferFundsAction(input: TransferFundsInput) {
  const session = await auth();
  if (!session?.user?.id) {
    throw new Error('Unauthorized');
  }

  await db.account.decrement({
    where: { userId: session.user.id },
    data: { balance: { decrement: input.amountInCents } },
  });

  await db.account.increment({
    where: { userId: input.recipientId },
    data: { balance: { increment: input.amountInCents } },
  });

  revalidatePath('/dashboard');
  return { success: true };
}
```

#### Production Standard (Correct)
> **Standard**: The mutation requires an ephemeral nonce cryptographically tied to the user's ID, the specific action intent, and a strict 60-second validity window. `verifyAndConsumeNonce` uses constant-time validation and atomically marks the token consumed to permanently foreclose replay attacks.
```typescript
'use server';

import { auth } from '@/lib/auth';
import { db } from '@/lib/db';
import { verifyAndConsumeNonce } from '@/lib/security/nonce';
import { revalidatePath } from 'next/cache';

interface TransferFundsInput {
  recipientId: string;
  amountInCents: number;
  actionNonce: string;
}

// SECURE INVARIANT: Cryptographically bound execution nonce validated and atomically consumed
export async function transferFundsAction(input: TransferFundsInput) {
  const session = await auth();
  if (!session?.user?.id) {
    throw new Error('Unauthorized');
  }

  // Verifies signature, max 60s TTL, bound userId, and ensures single-use via KV/Cache
  const isAuthorizedExecution = await verifyAndConsumeNonce({
    nonce: input.actionNonce,
    expectedAction: 'transferFunds',
    expectedUserId: session.user.id,
    maxAgeSeconds: 60,
  });

  if (!isAuthorizedExecution) {
    throw new Error('Invalid, expired, or replayed execution nonce.');
  }

  await db.$transaction(async (tx) => {
    await tx.account.decrement({
      where: { userId: session.user.id },
      data: { balance: { decrement: input.amountInCents } },
    });

    await tx.account.increment({
      where: { userId: input.recipientId },
      data: { balance: { increment: input.amountInCents } },
    });
  });

  revalidatePath('/dashboard');
  return { success: true };
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Next.js Security Inspector
Analyzes Next.js Server Action entry points to identify unbound mutations and missing CSRF/nonce mitigations.
Recommended Agent Skills (askills.dev)

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

Web Crypto Auditor
Audits server-side cryptosystems to verify timing-safe comparisons and entropy adequacy across Next.js actions.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Next.js 15 Server Action Ephemeral Cryptographic Nonce-Binding Standard

Next.js 15 Server Action Ephemeral Cryptographic Nonce-Binding Standard defines an industrial-grade behavioral standard for security engineering. Next.js 15 Server Actions must enforce cryptographic nonce-binding to neutralize distributed replay attacks and session-riding state transitions. Every mutation-bearing Server Action must validate an ephemeral, HMAC-signed execution nonce strictly coupled to the authenticated user's session identifier, timestamp bounds, and mutation signature. State-changing operations must reject unverified payloads, guarantee single-use consumption, and strictly enforce atomic invalidation. 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: Executing Naked State Mutations in Next.js Server Actions Without Ephemeral Cryptographic Nonce Verification 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 DriftExecuting Naked State Mutations in Next.js Server Actions Without Ephemeral Cryptographic Nonce VerificationCritical
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 verify a cryptographically signed execution nonce before executing state-changing business logic in Server Actions.

Engineers MUST ALWAYS verify a cryptographically signed execution nonce before executing state-changing business logic in Server Actions.

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 trust Next.js Host/Origin headers alone to guard critical financial, authorization, or destructive mutations against replay attacks.

Engineers MUST NOT trust Next.js Host/Origin headers alone to guard critical financial, authorization, or destructive mutations against replay attacks.

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 MUST bind the session identity (e.g., userId or sessionId) directly into the signed nonce payload to prevent cross-session token migration.

Code MUST bind the session identity (e.g., userId or sessionId) directly into the signed nonce payload to prevent cross-session token migration.

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 implement constant-time comparison (e.g., crypto.timingSafeEqual) when validating HMAC signatures on action tokens.

Services MUST implement constant-time comparison (e.g., crypto.timingSafeEqual) when validating HMAC signatures on action tokens.

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 NEVER render form actions or invoke mutations without injecting an ephemeral nonce issued by an authoritative server component or session token provider.

Components NEVER render form actions or invoke mutations without injecting an ephemeral nonce issued by an authoritative server component or session token provider.

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 Next.js 15 Server Action Ephemeral Cryptographic Nonce-Binding Standard critical for AI coding assistants?

Next.js 15 Server Actions must enforce cryptographic nonce-binding to neutralize distributed replay attacks and session-riding state transitions. Every mutation-bearing Server Action must validate an ephemeral, HMAC-signed execution nonce strictly coupled to the authenticated user's session identifier, timestamp bounds, and mutation signature. State-changing operations must reject unverified payloads, guarantee single-use consumption, and strictly enforce atomic invalidation. 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 (Executing Naked State Mutations in Next.js Server Actions Without Ephemeral Cryptographic Nonce Verification) 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 SECURITY Rules

View all rules →
security
105

OpenFGA Graph Invariants: Cyclic Relation Prevention & Contextual Tuple Hardening

Enforces strict directed acyclic graph (DAG) topology validation during relationship mutation writes and mandates strict server-side schema verification for ephemeral contextual tuples in OpenFGA evaluations. Prohibits persistent storage of ephemeral request attributes and guards against recursive relation loops causing graph expansion denial-of-service.

security
81

WebAuthn Conditional UI Mediation, Nonce Atomicity, and Assertion Cryptographic Verification

Enforces zero-trust cryptographic validation for FIDO2/WebAuthn Passkey authentication with Conditional UI autofill. Requires atomic single-use challenge consumption to eliminate replay attacks, strict RP ID hash and origin binding, authenticatorData flag verification (User Presence and User Verification), and monotonic signature counter enforcement to detect authenticator cloning.

security
111

Enforce Sigstore Keyless OIDC Attestation and Admission Controller Verification

Enforces immutable supply-chain security using Sigstore Cosign keyless signing via ephemeral OIDC tokens issued by Fulcio and verified against the Rekor transparency log. Container workloads must be signed and attested at build time by digest, and admission controllers (such as Kyverno or Sigstore Policy Controller) must strictly validate the OIDC issuer and subject identity before allowing image execution.

1 Rule in Stack

Next.js