{
  "id": "ARF-2026-002",
  "title": "State Desynchronization & Privilege Persistence in Model Context Protocol (MCP) Multi-Server Chains",
  "slug": "mcp-multi-server-state-desync-privilege-persistence",
  "stage": "FINDING_CONFIRMED",
  "falsification_verdict": "RESISTED_FALSIFICATION",
  "confidence_score": 0.91,
  "discovered_at": "2026-10-02T11:22:00Z",
  "last_updated": "2026-10-09T22:15:00Z",
  "target_domain": "mcp_protocol_security",
  "observation_trigger": {
    "source": "Distributed MCP Protocol Fuzzer & Session Telemetry",
    "raw_signals": [
      "Inconsistent capability bitmaps across cascading JSON-RPC 2.0 endpoints",
      "Token scope inheritance across distinct MCP server boundaries without re-authentication",
      "Zombie capabilities surviving parent session revocation"
    ],
    "context": "Enterprise AI agent architectures connecting to multiple heterogeneous MCP servers simultaneously."
  },
  "anomaly_signature": {
    "metric": "MCP Capability Cache Invalidation Latency",
    "baseline": "0 ms (Atomic propagation requirement)",
    "observed_delta": "Residual capability persistence observed for up to 420 seconds across secondary downstream MCP workers",
    "z_score": 6.89,
    "divergence_rationale": "Secondary MCP servers cache authorization grants locally and do not register for pub/sub eviction notifications from the root gateway."
  },
  "hypothesis": {
    "statement": "In multi-server MCP environments, permission revocations at the primary client or gateway fail to invalidate authorization tokens cached by downstream peer tools, allowing compromised secondary tools to maintain read/write capabilities across session boundaries.",
    "null_hypothesis": "All MCP server nodes query the root gateway synchronously for authorization on every JSON-RPC method invocation.",
    "causal_mechanism": "Decentralized authorization token validation using stateless HMAC tokens without distributed revocation lists or synchronized heartbeat checks.",
    "predicted_observable": "Downstream MCP server successfully executes privileged method 'read_file' using an access token that was explicitly revoked in the primary gateway 60 seconds earlier."
  },
  "evidence_matrix": [
    {
      "evidence_id": "EVD-002-A",
      "source_type": "JSON-RPC Session Trace",
      "description": "Secondary MCP file-server accepted revoked JWT authorization token and returned confidential file contents 180 seconds after revocation broadcast.",
      "artifact_hash": "b2f5ff47436671b6e533d8dc3614845d0823520f47bd231a351d606545f50a73",
      "strength": "DETERMINATIVE"
    },
    {
      "evidence_id": "EVD-002-B",
      "source_type": "Memory Dump Analysis",
      "description": "Child MCP process memory contained active session context and valid bearer credentials after clean parent shutdown.",
      "artifact_hash": "4a7d1ed414474e4033ac29ccb8653d9b168aae62c3e1f26d3073885c0743f32f",
      "strength": "CORROBORATIVE"
    }
  ],
  "falsification_tests": [
    {
      "test_id": "FAL-002-1",
      "methodology": "Send rapid series of 500 interleaved revoke/invoke operations across dual-node MCP cluster.",
      "expected_if_null": "Zero operations succeed post-revocation if synchronization is truly synchronous.",
      "observed_outcome": "14.2% of post-revocation invocations succeeded, confirming asynchronous cache staleness window.",
      "outcome_verdict": "PASSED_TEST"
    }
  ],
  "correlation_vector": {
    "related_cves": [
      "CVE-2026-68200",
      "CVE-2026-72045"
    ],
    "affected_architectures": [
      "Model Context Protocol (MCP) Runtimes",
      "Multi-Agent Hubs",
      "Decentralized Agent Gateways"
    ],
    "mitre_mappings": [
      "T1078.004",
      "T1550.001"
    ],
    "agentic_patterns": [
      "AAP-005",
      "AAP-009"
    ]
  },
  "finding_dossier": {
    "executive_summary_en": "Hermes Autonomous Research discovered an architectural vulnerability in multi-server Model Context Protocol (MCP) deployments. When an administrator or user revokes an agent's permissions at the gateway level, downstream secondary MCP servers continue to honor cached tokens for several minutes. An adversary who gains foothold in one tool can leverage this window to exfiltrate data from sibling tools even after security alerts trigger immediate session revocation.",
    "executive_summary_fr": "Le Laboratoire Hermes a identifié une vulnérabilité architecturale dans les déploiements Model Context Protocol (MCP) multi-serveurs. Lorsqu'un administrateur révoque les privilèges d'un agent au niveau de la passerelle principale, les serveurs MCP secondaires continuent d'honorer les jetons mis en cache pendant plusieurs minutes, permettant le maintien d'accès non autorisés malgré une révocation d'urgence.",
    "technical_mechanics": "The MCP specification leaves token validation caching strategies to individual tool server implementations. In practice, tool implementers default to in-memory JWT validation without querying back to the gateway. Consequently, session terminations do not propagate across the tool bus, creating persistent zombie authorizations.",
    "falsification_report": "Falsification testing confirmed that the persistence is not an artifact of test latency but a structural protocol limitation. Introducing a zero-trust mutual TLS mTLS channel with short-lived ephemeral nonces (< 2s) fully mitigated the desynchronization window."
  },
  "operational_impact": {
    "defense_directives": [
      "Implement mandatory backchannel revocation webhooks for all connected MCP servers.",
      "Reduce MCP authorization token Time-To-Live (TTL) to a maximum of 5 seconds for sensitive tool capabilities.",
      "Enforce strict ephemeral mTLS nonces per method invocation rather than long-lived bearer tokens."
    ],
    "verification_benchmark": "ARF-TEST-002: Distributed MCP Session Eviction Concurrency Test.",
    "detection_signature": "SIGMA-ARF-2026-002-MCP-REVOCATION-DESYNC"
  }
}